On Sun, Mar 25, 2007 at 06:59:30PM -0600, JB wrote:
> So there is an option to use the architecture specific string libc
> functions that was selected by default. I missed that while reviewing
> the configuration. Configuring uClibc to not use the architecture
> specific functions solved it...now happily compiling...
>
If you're feeling more adventurous, you could load the CPU flags from the
kernel in to ELF_HWCAP in the auxvt, and figure out at runtime whether
you have ll/sc capabilities or not. This way you can at least retain ABI
compatability. Plenty of other architectures do similar things for their
atomics already in glibc. You're still going to need kernel-level ll/sc
emulation for existing applications, though.
_______________________________________________
uClibc mailing list
[EMAIL PROTECTED]
http://busybox.net/cgi-bin/mailman/listinfo/uclibc
