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] |
Titus, All, On Monday 17 May 2010 14:43:02 Titus von Boxberg wrote: > > 5 U wrapper-compile-commandline: > > Breaks canadian-cross: do not use cc, but really _do_ use ${CT_HOST}-gcc > > You can't -D${CT_SYS_OS} because it can be something like: GNU/Linux > > and this is not a valid macro name. Or we just always use: uname -s > > (and get rid of uname -o) > > Space damage. > Calls to ${CT_HOST}-gcc do not work anymore on MacOS. That's strange, because we ought to have at least build-tools wrappers, in scripts/crosstool-NG.sh.in@381 and removed inscripts/build/internal.sh@82, that is after the wrapper is built. > Is it ok for you if I define a new variable, say CT_HOST_GCC, > and if I replace the three or so calls of ${CT_HOST}-gcc with it? Before, I'd like to understand why it does not work. I guess the canadian case works, as we know we have a cross-gcc for that, but the case that seems to be an issue is the standard cross build. Right? Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- 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] |