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] |
> WE are working on a project related to MPC-850 and we need to build up the > gcc as a cross compiler on a 686 host might be with uclibc. We started > with crosstool. We found it great.... BTW, I've been working on getting crosstool to work with uClibc. I hope to have an announcement of success today (crosses fingers) -- I got a build to go all the way to libstdc++v3 before I left last night. It died there because I had configured wide-char support out of uClibc. I just noticed this morning that when buildroot (the vaguely crosstool-like tool that the uClibc project recommends using) builds, it always forces wide-char and locale support on, presumably because gcc needs those for C++. For my project, we want a fairly minimal uClibc. So what I think I might do for my crosstool-uClibc patch is only force wide-char and locale support on if you *haven't* told crosstool that you specifically only want a C compiler for the final gcc build (rather than the default of C and C++). I'll do builds without specifying that, work on that until I get a clean complete build, then add the C-only crosstool options for my project's build. And when THAT works, I'll get a mega-patch on its way to Dan. -----Carl ------ 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] |