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] |
Hi Dave, Your web site is excellent. Thanks for the info. Should I just begin with gcc-2.95.4? I started with binutils-2.10 and gcc-2.95.3 source. Then applied the patches you recommended. Binutils built just fine. However for gcc-2.95.3 here is the story: 1st: ----------------------------------------------------------------------- /usr/local/obj/gcc2.95.3-ppc/gcc/include/sys/stat.h:131: parse error before `fstatfs' /usr/local/obj/gcc2.95.3-ppc/gcc/include/sys/stat.h:131: warning: data definition has no type or storage class /usr/local/obj/gcc2.95.3-ppc/gcc/include/sys/stat.h:132: parse error before `statfs' /usr/local/obj/gcc2.95.3-ppc/gcc/include/sys/stat.h:132: warning: data definition has no type or storage class /usr/local/src/gcc-2.95.3-vxWorks/libiberty/fdmatch.c: In function `fdmatch' /usr/local/src/gcc-2.95.3-vxWorks/libiberty/fdmatch.c:59: storage size of `sbuf1' isn't known /usr/local/src/gcc-2.95.3-vxWorks/libiberty/fdmatch.c:60: storage size of `sbuf2' isn't known gmake[1]: *** [fdmatch.o] Error 1 gmake[1]: Leaving directory `/usr/local/obj/gcc2.95.3-ppc/powerpc-wrs-vxworks/libiberty' gmake *** [all-target-libiberty] Error 2 -------------------------------------------------------------- I added #include <types/vxTypesOld.h> to stat.h and the 1st error went away. 2nd Error: -------------------------------------------------------------- /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:101: macro `__VA_GP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:101: macro `__VA_GP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:101: macro `__VA_GP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:105: macro `__VA_FP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:105: macro `__VA_GP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:105: macro `__VA_GP_REGSAVE' used with too many (3) args /usr/local/src/gcc-2.95.3-vxWorks/libiberty/vasprintf.c:105: macro `__VA_GP_REGSAVE' used with too many (3) args gmake[1]: *** [vasprintf.o] Error 1 gmake[1]: Leaving directory `/usr/local/obj/gcc2.95.3-ppc/powerpc-wrs-vxworks/libiberty' gmake: *** [all-target-libiberty] Error 2 ------------------------------------------------------------------------- Thanks, Ernest >===== Original Message From Dave Korn <davek-ml@ntlworld.com> ===== >----- Original Message ----- >From: "Ernest L. Williams Jr." <ernesto@ornl.gov> >Sent: Saturday, October 27, 2001 2:05 AM > >> I am trying to build a cross-compiler for the following scenario: >> 1. HOST = BUILD = Linux on a x86 >> 2. Target = MVME2101 (i.e. PowerPC 603e a.k.a MPC8240) >> 3. The operating system (i.e. BSP) running on the target is vxWorks 5.4.2 >> >> I am using the source distribution of the following packages: >> 1. binutils-2.11.2 >> 2. gcc-3.0.2 > > Can't really recommend that combination: the C++ stuff in the compiler >will be 100% incompatible with the C++ support in the kernel; gcc v3 has a >new C++ abi, objects are laid out differently, function names mangled >differently, etc. Even the basic C support is incompatible in the way it >aligns double precision floating point function parameters on the stack, >although that was the case in 2.95.x as well - the powerpc-wrs-vxworks >target is a little bit-rotted. > >> I have already tried gcc-2.95.3 and gcc-3.0.1. > > I'd recommend binutils 2.10 with gcc 2.95.3 or .4, and apply the patches >from my website http://www.newgcc4vxworks4ppc.cjb.net/ where I've got two >patchsets: one for fixing 2.95.3 to just work with powerpc-wrs-vxworks and >be compatible with the OS, another for adding altivec support. You won't >need that for the 603, but it's also based on a slightly more up-to-date and >bugfixed version of the 2.95 series. Watch out for MSDOS vs. UNIX >end-of-line difficulties with my files though, I generated them all on a pc >under cygwin. > >> I thought maybe for once all of the necessary fixes would be in the >> gcc-3.0.2 release. > > WRS have been not-quite-getting-round-to updating the vxworks/ppc port in >the main FSF tree for years now. > > DaveK >-- >Burn your ID card! http://www.optional-identity.org.uk/ >Help support the campaign, copy this into your .sig! SNS Controls Group ------ 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] |