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, 2010/1/28 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>: > Hello Remy, All! > > Whaoo! Very nice! Thank you for the submission! :-) > > I have however a few questions, see below... > > On Thursday 28 January 2010 19:57:14 Remy Bohmer wrote: >> +config ARCH_m68k >> + ? ?select ARCH_SUPPORTS_32 >> + ? ?select ARCH_DEFAULT_32 >> + ? ?select ARCH_DEFAULT_BE >> + ? ?select ARCH_SUPPORT_CPU > > From the gcc man page, it seems you can also pass -march and -mtune. > Did you exclude those on purpose, or is it a oversight? Looking deeper into this it seems that: * if GCC is compiled with --with-arch=m68k (ARCH_ARCH=m68k) then the build of newlib eventually fails because its compilation passes -march=m68k to GCC, which is an illegal value for GCC itself. * If GCC is compiled with 'ARCH_ARCH=cpu32', which is valid for -march for GCC as listed on the man-pages, then the compilation of GCC fails since it does not like this option to be passed through --with-arch. * --with-tune is not supported either, although --with-cpu works properly. Any ideas? Kind regards, Remy -- 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] |