This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello, On Tue, Jan 06, 2004 at 07:45:36AM -0800, Dan Kegel wrote: > >Its hard to know, but a number of autoconf macros rely on the values > >generated by config.guess. > > Oddly, config.guess doesn't contain the string 'uclibc' or 'uclinux'. > Wonder what it outputs when running on a uclibc system... It returns <ARCH>-<*>-linux-gnu, but that is easy enough to fix. > Here's some discussion from when Bernardo was picking the system name: > http://gcc.gnu.org/ml/gcc-patches/2003-09/msg01136.html > which notes that *-uclinux-uclibc is a good tuple which is significantly > different from *-linux-uclibc in that it uses flat ELF files > rather than normal ones. > > Does anyone know if any program needs to behave differently for > *-linux-uclibc > as opposed to *-linux-gnu (besides gcc)? I imagine it might > change a couple defaults in the cross-compile case for some autoconf tests, > at least... We really need a seperate tuple in order to coexist with glibc. For what it is worth, I just about have binutils-2.14.90.0.6 and gcc-3.3.2 building "normally" for *-linux-uclibc. I'm hoping to have that finished by the end of he week. I still need to work around some stdlibc++/locale issues. Manuel ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |