Brian Gerst wrote:
> > Ouch. So lemme think...is it possible for some code macro to detect
> > it's being compiled pic on the x86 and use alternate macros that
> > save the appropriate registers?
> Look at the source to Glibc. They have to deal with this issue.
I have to wonder why Glibc's <sys/syscall.h> doesn't define these
macros, but instead includes <asm/unistd.h> which is a kernel header.
Here is a fine example of something that should not be using the kernel
header. Glibc should define the macros, and include PIC-safe varieties.
The fix here is to file a bug report for Glibc.
Or you could just use the syscall() function from Perl ;-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Aug 07 2000 - 21:00:11 EST