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] |
let me ask a simpler question regarding this whole sysroot thing, then. what is the advantage in selecting a USE_SYSROOT build when running crosstool? what do i get out of it?
IIRC, there was no other way to get a working x86_64 toolchain. Dunno why.
so the questions remains -- if i use a sysroot approach in building my toolchain, do i have any need for that sys-root directory afterwards? is it necessary for the *use* of the toolchain once it's been built?
There are a few things currently outside the sysroot directory that ought to be moved inside (e.g. the c++ libraries), but there's nothing bad about the current situation other than a little untidiness, I think. - Dan
-- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------ 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] |