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] |
Joel Sherrill wrote:
But many targets don't use glibc. Many use newlib and others use yetI think such packages already exist: it's the union of glibc, binutils, and gcc. All that's missing is the ueber-build directory and/or the build-it-all script.But where would we get header files for it?Oh, you'd need to supply a set of kernel headers, too. But those come straight from the kernel source. Anything else the build script should generate from the gnu source (gcc/glibc/binutils/etc).
other C libraries. I recall avr and msp430 having their own C libraries and
it is pretty clear at this point that the TI C3x/4x ports will have to have
custom libm's to be any good.
Yes, it's quite clear gcc needs to be used with C libraries other than glibc. > So you will be shippng some huge,
inordinately complicated set of source.
? Not sure what you're talking about there. All I said was that Gnu should have a build script that knows how to build a complete working toolchain given the gcc, binutils, and glibc source tarballs. That doesn't preclude anyone from maintaining a build script that builds a complete working toolchain from, say, gcc, binutils, and dietlibc... and it doesn't mean that gnu should release gcc only as a bundle with glibc. - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |