From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kai Ruottu To: egcs@cygnus.com Cc: Dick Munroe , crossgcc@sourceware.cygnus.com Subject: Re: Trying to build a cross compiler from linux to netbsd... Date: Fri, 05 Jan 2001 03:59:00 -0000 Message-id: <3A55926F.173D2B6@luukku.com> References: <3A5293AF.CC95CA6E@csworks.com> <3A544322.E541D76A@luukku.com> X-SW-Source: 2001-01/msg00035.html 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kai Ruottu To: egcs@cygnus.com Cc: Dick Munroe , crossgcc@sourceware.cygnus.com Subject: Re: Trying to build a cross compiler from linux to netbsd... Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-ID: <3A55926F.173D2B6@luukku.com> References: <3A5293AF.CC95CA6E@csworks.com> <3A544322.E541D76A@luukku.com> X-SW-Source: 2001-q1/msg00035.html Message-ID: <20010401000000.cg9ASZDnYIVnz7Vd9Vb-MhsIabmCvwOLl9qS8rI_9iY@z> 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