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] |
Other format: | [Raw text] |
Thanks to all for the help/suggestions. Using Jay's build script I've been able to build all the tools/libraries for the powerpc-eabi toolchain. Can anyone point me at docs pertaining to the differences between the powerpc-eabi and powerpc-eabispe target tools? Based on some reading I did this morning I realized I may not have built all I need (yet). I had previously thought the powerpc-eabi covered all PPC target families, including BookE processors. Is this incorrect? I need to support PPC750, MPC82xx (PPC603e core), PPC74xx, and MPC85xx (e500 core - is BookE) target processors and link with the VxWorks (v5.4 & 5.5 OS). Is the powerpc-eabi tool chain going to do it for me or do I need a separate toolchain for powerpc-eabispe to handle the BookE processors? I looked for VxWorks specific patches, but I didn't see any. Does anyone know if I missed something? Thanks, Jon Watson -----Original Message----- From: Jay.Kulpinski@gd-ais.com [mailto:Jay.Kulpinski@gd-ais.com] Sent: Thursday, August 26, 2004 1:42 PM To: Jon Watson Cc: crossgcc@sources.redhat.com Subject: Re: Help w/ gcc cross build failing On Thursday 26 August 2004 01:01 pm, Daniel Kegel wrote: > Jon Watson wrote: > > After unpacking the distribution .tar.gz files I created a subdir called > > build and ran configure (from the build subdir) like this: > > > > ../configure --target=powerpc-eabi > > --prefix=/cygdrive/c/gnutools/gcc-3.4.1 --without-headers > > --with-as=/cygdrive/c/gnutools/binutils-2.14/powerpc-eabi/bin/as > > --with-ld=/cygdrive/c/gnutools/binutils-2.14/powerpc-eabi/bin/ld > > --with-local-prefix=/cygdrive/c/gnutools/gcc-3.4.1/powerpc-eabi > > --disable-shared --disable-win32-registry > > > > I have already built the binutils (2.14) for powerpc-abi. I installed the > > binutils (for powerpc-abi) in a separate subdir I'm using for the tool > > chain I'm trying to build. I always use the same prefix for binutils, gcc, and newlib. > > > > I still had to edit the generated Makefiles to get them to use the right > > binutil tools for the powerpc-eabi target. The changes were very minor - > > I just filled in the definition of the variables like AR_FOR_TARGET. > > You should not have to hand edit anything. > In particular, did you make sure your binutils were on the PATH? > configure will use $TARGET-ar for AR_FOR_TARGET if it sees it on the PATH. > You should definitely include your prefix/bin directory in your $PATH before you start the build. > > Please try Jay's script, or at least read and understand it. > Otherwise you're going to run into lots and lots of roadblocks, > and each time we answer one of your questions, it'll be something > that Jay's script would have shown you how to do, I bet. > - Dan ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |