Well, I'm back. I didn't get any help from the uClibc folks, but I eventually
figured out how to get to the waitid function in the kernel using the _syscall4
macro and the right header file. waitid worked great, but then I started
having problems when more than one child needed to be reaped.
Well, I'm back. I didn't get any help from the uClibc folks, but I eventually
figured out how to get to the waitid function in the kernel using the _syscall4
macro and the right header file. waitid worked great, but then I started
having problems when more than one child needed to be reaped.
You're asking the wrong list. Try the uClibc list at uclibc.org.
glibc and uClibc provide C APIs to kernel system calls. uClibc doesn't
implement all features that glibc supports - there are several kernel
APIs that uClibc doesn't expose. Ask the uClibc folk for advice.
--
James Chapman
Can anyone help with this?
We have an application that runs fine on our linux workstations, but
will not compile to run on a new target. This application is using
the WNOWAIT option for the waitid() function. When the source file is
compiled for the target using powerpc-uclibc-gcc, it fails
Can anyone help with this?
We have an application that runs fine on our linux workstations, but
will not compile to run on a new target. This application is using
the WNOWAIT option for the waitid() function. When the source file is
compiled for the target using powerpc-uclibc-gcc, it fails
You're asking the wrong list. Try the uClibc list at uclibc.org.
glibc and uClibc provide C APIs to kernel system calls. uClibc doesn't
implement all features that glibc supports - there are several kernel
APIs that uClibc doesn't expose. Ask the uClibc folk for advice.
--
James Chapman
6 matches
Mail list logo
