This is the mail archive of the crossgcc@sources.redhat.com 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] |
Corrections... Kai Ruottu wrote: > > There was only one issue I fixed while building... Somehow the 'tm.h' had: > > #define TARGET_CPU_DEFAULT 1 > #include "i386/netbsd.h" > > while the 'gcc/config/i386/netbsd.h' had another definition for TARGET_CPU_DEFAULT, > The definition in 'gcc/config/i386/netbsd.h' could be checked : > #define TARGET_CPU_DEFAULT 0400 /* TARGET_NO_FANCY_MATH_387 */ > > The '0400' sounds more sane than '1', but checking what these 'TARGET' bits > mean from the 'gcc/config/i386/i386.h' could be recommended. I somehow mixed the TARGET_CPU_DEFAULT in my mind with the TARGET_DEFAULT bit-collection. The '1' is sane and means that the default target-CPU will be '486', '0' is '386', '2' is '586' or 'pentium' and so on... The '1' came because of my target name 'i486-netbsd'. The same error was made the port-maker, later GCCs have the 'netbsd.h' corrected by removing the '#define TARGET_CPU_DEFAULT 0400' garbage. Also the 'freebsd.h' had the same definition in egcs-1.0.3a and egcs-1.1.2 sources and removed from the later ones. Is it really sure that only egcs-1.0.3a can be used for NetBSD/aout ? Someone has maintained the port in the newer GCCs and there are quite a lot fixes, not only that for the TARGET_CPU_DEFAULT... Cheers, Kai ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |