| Age | Commit message (Collapse) | Author |
|---|
|
the already existing clock_gettime(). In addition they will now use
the corresponding system calls if they exists, which resulted in a
move to libc/sysdeps/linux/common for clock_gettime.c (it was
previously located in libc/misc/time).
|
|
|
|
it alphabetized (which was not fully successful) made adding a new
file a mess. Replaced it with a call to the make function $(wildcard).
|
|
syscalls. This won't work on 2.2 kernels(I think).
|
|
|
|
|
|
|
|
define was no longer visible to vasprintf. I didn't catch this since I no
longer use such old tools. Unfortunately, some well-meaning but misguided
individual decided to just cut-and-paste the macro. :-(
Try to clean up the situation by putting it into a header that can be overriden
by any archs that need to. If this breaks for anyone (as I said, I no longer
use such old tools and so haven't tested), let me know and I'll fix it.
|
|
priority if successful, while the linux syscall returns 0. Also, in
the non-syscall version, we must be sure to set errno to EPERM on failure
since setpriority() can set errno to several possible values.
Note: The version of glibc on my debian system is broken wrt EPERM too.
|
|
umount() actually works :)
|
|
|
|
|
|
|
|
|
|
|
|
try to emulate umount() using umount2()
|
|
but neither __NR_fadvise64 nor __NR_fadvise64_64.
|
|
|
|
|
|
Some newer archs only have umount2
|
|
|
|
|
|
|
|
Here is a small patch to add epoll support to uclibc.
The only thing I am not sure about is what needs to be done (if anything)
to make it work on 2.4/2.2 kernels (are the syscall numbers defined but
give errors when called or not?).
Tested on 2.6, though some other issues prevent more extensive testing at
the minute.
Mike Frysinger:
cleaned up patch and added checks to make sure that the syscall actually
exists, returning ENOSYS in cases where it doesn't.
|
|
|
|
rename UCLIBC_PROPOLICE to UCLIBC_HAS_SSP
|
|
|
|
using uClibc. mincore() and the ones for Extended Attributes setxattr(), lsetxattr(), fsetxattr(), getxattr(), lgetxattr(), fgetxattr(), listxattr(), llistxattr(), flistxattr(), removexattr(), lremovexattr(), fremovexattr() which are optional.
|
|
> What's the correct way of calling llseek/_llseek?
> The manpage I have indicates _llseek and thats what the version of
> util-linux
> I tried use as well so compiling for uClibc fails.
> Would the following patch fix it or is it the apps that needs fixing?
|
|
|
|
|
|
enabled. syslog() support should now work both inside and outside of chroots. erandom code left in but remains #ifdef out by default. May remove erandom completely in the future for uClibc unless the LFS guys and gals want to keep it.
|
|
enabled. syslog() support should now work both inside and outside of chroots. erandom code left in but remains #ifdef out by default. May remove erandom completely in the future for uClibc unless the LFS guys and gals want to keep it.
|
|
was incorrect in uClibc, and was 2 bytes too short. This caused uClibc
shared memory stuff to not behave correctly since struct ipc_perm was
included as the first member of, i.e. struct msqid_ds, so the content
of that struct were all shifted by two bytes. ugh. Apparently, few
people have used shared memory, msgctl(), etc with uClibc thus far,
-Erik
|
|
adding cruft to include/sys/time.h. But also, there's no sense in
making changes like this until we decide how we're going to approach
the hidden symbol transition.
|
|
Hello!
Would the attached patch be acceptable (maybe instead of
__libc_gettimeofday using __gettimeofday)
We have some issues, see
http://bugs.gentoo.org/show_bug.cgi?id=65892
|
|
|
|
more sane than 'gcc -pg' and seems much easier to support.
-Erik
|
|
size and performance penalty to profiling applications this way, as well as
Heisenberg effects, where the act of measuring changes what is measured.
There are better tools for doing profiling, such as OProfile, that do not
require gcc to instrument the application code.
-Erik
|
|
-Erik
|
|
_dl_pagesize variable in ldso, so avoid aliasing.
-Erik
|
|
-Erik
|
|
|
|
Some utilities, such as valgrind, have a legitimate reason to know the address
of the current brk. Since we know such utils will peek under our skirt, we
might as well give them what they expect and not use a gratuitously different
symbol name.
-Erik
|
|
are being used
|
|
-Erik
|
|
|
|
|
|
by extracting the value from the ELF header.
|
|
|
