Re: [m68k] Restore some original predefines and cleanup m68k targetflags

[Hans-Peter Nilsson <hp at bitrange dot com>]

On Sat, 20 Sep 2003, Bernardo Innocenti wrote:
> No, no! You've just misunderstood me. My target tuple is
> just "m68k-linux-uclibc". m68k-linux-uclibc-gcc is what
> the installed compiler ends up being called.

Ah, ok.

> > Still, I *do* recommend
> > m68k-unknown-uclinux or preferrably m68k-unknown-uclinux-uclibc
> > for the reasons pointed out in the thread ending(?) at
> > <URL:http://gcc.gnu.org/ml/gcc-patches/2003-09/msg01191.html>.
>
> I would agree with you on using uclinux in place of linux, but
> then would I really need to append -uclibc to it?

I can imagine other libraries being used with uclinux than
uclibc.  There was even an attempt to use glibc, but there
were... problems.

> uclibc is compatible enough with glibc to share the libstdc++
> config/os/gnu-linux subdirectory with just a few lines of
> fixes.

With a proper configuration you wouldn't need "a few lines of
fixes", right?  Either way, uclibc is still not glibc and I
doubt it has yet implemented the finer points of C++ and thread
support.  Don't be blinded by whatever gcc uses and matches
configure-wise.

FWIW I think I know quite well what uclibc is; I bump into it
from time to time. :-)  Most Axis camera products of a few years
ago [for example the 2100, IIRC] should be described as
cris-axis-uclinux-uclibc.

> You might think of uClibc as yet another version of glibc.
> It even defines __GLIBC__. Application code and autoconf can
> tell them apart using the __UCLIBC__ preprocessor symbol.
>
> I just need to make up something different from m68k-linux,
> and m68k-uclinux is easier to type than m68k-linux-uclibc.

Also, m68k-linux-uclibc would indicate a (MMU-enabled) linux
using uclibc (cris-axis-linux-uclibc certainly exists) so that'd
be wrong.

brgds, H-P