[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fZqCW0tc0_9XnLZE6x6g1dLA6_61uZsXNQaT1k9hqWbJmMVw@mail.gmail.com>
Date: Thu, 21 Dec 2017 17:25:31 +0100
From: ardi <ardillasdelmonte@...il.com>
To: musl@...ts.openwall.com
Subject: Feature request: building musl in a portable way
Hi,
Related (and as an alternative) to a previous post I made asking about
a way of isolating direct syscalls, I'm thinking about the possibility
of building musl in a way where functions that need to perform
syscalls aren't compiled, so this special compiled version of musl
would have only the functions that don't make syscalls from
themselves.
The purpose is being able to run code in system other than Linux,
replacing such functions by calls to the related functions of the
system host (provided that functions follow POSIX requirements, of
course).
Obviously, I can get this feature by modifying musl, but I'd prefer
not to modify it, because I'd like to be able to update musl to the
last version easily, and if I use a modified/customized musl version,
updating it would require merging, and possibly hard work.
If there was some way of having a switch in the build system so that
all functions that make syscalls are not compiled, I could use musl
without modifying it. Maybe the most elegant way of doing this would
be by tagging such functions with an special tag, like
"__function_makes_syscall__" or whatever. But I'm not sure.
Cheers, and thanks a lot,
ardi
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
