musl/include/sys, branch v0.9.3 musl - an implementation of the standard library for Linux-based systems add ioperm/iopl syscalls 2012-07-23T20:54:53+00:00 Rich Felker dalias@aerifal.cx 2012-07-23T20:54:53+00:00 d426b045332718ae6d42237303d657fd97c51455 based on patches by orc and Isaac Dunham, with some fixes. sys/io.h exists and contains prototypes for these functions regardless of whether the target arch has them; this is a bit unorthodox but I don't think it will break anything. the function definitions do not exist unless the appropriate SYS_* syscall number macro is defined, which should make sure configure scripts looking for these functions don't find them on other systems. presently, sys/io.h does not have the inb/outb/etc. port io macros/functions. I'd be surprised if ioperm/iopl are useful without them, so they probably need to be added at some point in appropriate bits/io.h files... 
based on patches by orc and Isaac Dunham, with some fixes. sys/io.h
exists and contains prototypes for these functions regardless of
whether the target arch has them; this is a bit unorthodox but I don't
think it will break anything. the function definitions do not exist
unless the appropriate SYS_* syscall number macro is defined, which
should make sure configure scripts looking for these functions don't
find them on other systems.

presently, sys/io.h does not have the inb/outb/etc. port io
macros/functions. I'd be surprised if ioperm/iopl are useful without
them, so they probably need to be added at some point in appropriate
bits/io.h files...
add extended attributes syscalls 2012-07-23T20:39:44+00:00 Rich Felker dalias@aerifal.cx 2012-07-23T20:39:44+00:00 207460d09742304941f1a010a89fc2efa46bcb29 based on patch by orc and Isaac Dunham, with some fixes. 
based on patch by orc and Isaac Dunham, with some fixes.
workaround another sendmsg kernel bug on 64-bit machines 2012-07-13T01:37:54+00:00 Rich Felker dalias@aerifal.cx 2012-07-13T01:37:54+00:00 96107564e2eabbc13800fe7a7d930b67216d0805 the kernel wrongly expects the cmsg length field to be size_t instead of socklen_t. in order to work around the issue, we have to impose a length limit and copy to a local buffer. the length limit should be more than sufficient for any real-world use; these headers are only used for passing file descriptors and permissions between processes over unix sockets. 
the kernel wrongly expects the cmsg length field to be size_t instead
of socklen_t. in order to work around the issue, we have to impose a
length limit and copy to a local buffer. the length limit should be
more than sufficient for any real-world use; these headers are only
used for passing file descriptors and permissions between processes
over unix sockets.
add process_vm_readv and process_vm_writev syscall wrappers 2012-06-24T01:38:47+00:00 Rich Felker dalias@aerifal.cx 2012-06-24T01:38:47+00:00 9cf9c39e48342a5d4007824d49b88132d93d83e3 based on a patch submitted by Kristian L. <email@thexception.net> 
based on a patch submitted by Kristian L. <email@thexception.net>
header file fixes: multiple include guard consistency and correctness 2012-06-16T01:52:53+00:00 Rich Felker dalias@aerifal.cx 2012-06-16T01:52:53+00:00 57d5fff5f7dd9af27152c84ce041c18597a22766 one file was reusing another file's macro name, and many had inconsistent underscores and application of SYS prefix, etc. patch by Szabolcs Nagy (nsz) 
one file was reusing another file's macro name, and many had
inconsistent underscores and application of SYS prefix, etc.

patch by Szabolcs Nagy (nsz)
fix sysinfo, try 2. it seems to work this time. 2012-06-08T03:06:04+00:00 Rich Felker dalias@aerifal.cx 2012-06-08T03:06:04+00:00 1429ce9ba2425b8abeefc311d56db5efe801d9d2 






sysinfo struct was utter nonsense; no idea where it came from.
2012-06-08T02:58:19+00:00

Rich Felker
dalias@aerifal.cx

2012-06-08T02:58:19+00:00

e86b18a63eb6b65e18e761212f69a0abc16b50b1

this broke the busybox "free" utility (memory reporting) and possibly
other things like uptime.





this broke the busybox "free" utility (memory reporting) and possibly
other things like uptime.







_GNU_SOURCE is supposed to imply _LARGEFILE64_SOURCE
2012-06-04T12:03:56+00:00

Rich Felker
dalias@aerifal.cx

2012-06-04T12:03:56+00:00

3b94daba711090f1936f59fae6f7cbcba963b29e

this is ugly and stupid, but now that the *64 symbol names exist, a
lot of broken GNU software detects them in configure, then either
breaks during build due to missing off64_t definition, or attempts to
compile without function declarations/prototypes. "fixing" it here is
easier than telling everyone to add yet another feature test macro to
their builds.





this is ugly and stupid, but now that the *64 symbol names exist, a
lot of broken GNU software detects them in configure, then either
breaks during build due to missing off64_t definition, or attempts to
compile without function declarations/prototypes. "fixing" it here is
easier than telling everyone to add yet another feature test macro to
their builds.







various header cleanups, some related to _BSD_SOURCE addition
2012-05-23T02:04:55+00:00

Rich Felker
dalias@aerifal.cx

2012-05-23T02:04:55+00:00

671ffab7769b4dfd873f0c585444823a67dc56bc

there is no reason to avoid multiple identical macro definitions; this
is perfectly legal C, and even with the maximal warning options
enabled, gcc does not issue any warning for it.





there is no reason to avoid multiple identical macro definitions; this
is perfectly legal C, and even with the maximal warning options
enabled, gcc does not issue any warning for it.







support _BSD_SOURCE feature test macro
2012-05-23T01:52:08+00:00

Rich Felker
dalias@aerifal.cx

2012-05-23T01:52:08+00:00

419ae6d5c95629d3ebaff6f1880d52cb027ba924

patch by Isaac Dunham. matched closely (maybe not exact) to glibc's
idea of what _BSD_SOURCE should make visible.





patch by Isaac Dunham. matched closely (maybe not exact) to glibc's
idea of what _BSD_SOURCE should make visible.