This is the mail archive of the crossgcc@sourceware.org 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] |
> OK, then I think it would make more sense to the gcc/binutils/gdb to > statically link against zlib, and it will use the available one: for > gcc, its bundled version; for glibc/gdb, the system static lib. > > Originally, the companion libraries are here to workaround missing or > too old libraries on the system. This made (and still makes) sense, as > those libraries are only available in recent distros, and older ones > are still, and will always be, lacking those. But as they are needed > by gcc, and not yet widely available, crosstool-NG has to build its > owns. > > But for more traditional libraries, I would highly prefer that crosstool-NG > uses the system libraries, even if it requires the user to install extra > packages. > > zlib, expat and ncurses are surely widely available nowadays, and it does > not make much sense in duplicating the effort to build them. > > So, I would suggest that we look at making the affected components link > statically (but optionally) against the host libraries, rather than > building our owns... > What's about canadian build for windows host? Do we have window version of zlib, expat and libiconv? Thanks! -Zhenqiang -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |