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] |
Hi, On Tue, Aug 24, 2010 at 07:22:28PM +0200, Yann E. MORIN wrote: > On Tuesday 24 August 2010 16:59:30 Johannes Stezenbach wrote: > > > --with-specs is not a valid, recognised option. So in this case, I'm not sure > > > how ./configure treats it. It seems it tries to assign the right-hand part > > > (after the '=' ) to the variable whose name in on the left-hand part (before > > > the '=' ). > > Maybe you need to add a new CT_CC_CORE_EXTRA_SPECS which uses > > quoting, e.g. > > The issue is not quoting here. It's the fact that '--wih-specs' is not an > option recognised bu ./configure. At least, it is not documented in the > gcc manual I pointed previously, and I could not see any reference to this > option in any of the gcc 22 configure scripts. OK, what led me to believe it is quoting issue is this: > > > > [ERROR] configure: error: invalid variable name: '--with-specs > The only place I've been able to see --with-specs=foobar is in conjunction > with the CodeSourcery toolchains, and it looks like this option is their > own 'invention'. http://gcc.gnu.org/ml/gcc-patches/2009-12/msg00132.html I'm not usre if this went into gcc-4.5 but I guess so. Best Regards Johannes -- 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] |