[uClibc] Query about uclinux/uclibc ABI and system tuple.

[Rob Landley]

Erik:

A new patch is wandering around for config.sub in various packages:

http://gcc.gnu.org/ml/gcc-patches/2003-10/msg01295.html

I'd like to ask you about this bit specifically:

-  nto-qnx* | linux-gnu* | linux-dietlibc | kfreebsd*-gnu* | knetbsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)
+  nto-qnx* | linux-gnu* | linux-dietlibc | linux-uclibc* | uclinux-uclibc* | uclinux-gnu* | \
+  kfreebsd*-gnu* | knetbsd*-gnu* | netbsd*-gnu* | storm-chaos* | os2-emx* | rtmk-nova*)

This is for the end bit of a system tuple ala "i386-pc-linux-uclibc".

A) I'm under the impression that uclinux will never use glibc, so
uclinux-gnu (end of the middle line) is an impossible target.  Is this
correct?

B) What's the ABI difference between uclinux-uclibc and linux-uclibc?
(uclinux uses uclibc, but is it significantly different than 

C) The uclinux abi currently changes based on version (hence the * at the end
for version info),  but also changes based on configuration.  Is there some
standard way to detect the configuration elements in a uclibc system that
change the abi, and somehow encode them in the version info on the end of the
string?  (A series of letters indicating non-default options, perhaps?
uclibc0.96tp, t for no threads, p for no position independent code?)

Is there a way to autodetect this stuff for config.guess?  (Some option to
ldd, perhaps?)

Comments?

Rob