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, > OK, gcc is clearly at fault here (IMHO). So it's the responsibility of the > gcc build script to fix those. From what I read in the GCC release notes was that the arch flag support for m68k was recently added, so it does not surprise me that it did not work properly. I guess it was added for Coldfire support. > Eg.: > - CT_ARCH_ARCH can take any value acceptable by -march > - the build script mangles that value to build a value suitable for > ?--with-arch Do you really want to work around GCC bugs in the ct-ng scripts? I would expect that patching GCC was the better approach... (i.e. adding patches in the ct-ng patches directory for GCC) > That's the idea... But I'm no m68k expert, here... Me neither ;-))) 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] |