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]

Re: Cross GCC for PowerPC and vxWorks


On Wed, 28 Dec 2005, Steven J. Magnani wrote:

> > Dan wrote:
> > Try 
> >
> http://web.archive.org/web/20040922201236/http://www.newgcc4vxworks4ppc.
> cjb.net/
> 
> Be careful - I discovered that if you go to "Patches" and click on the
> link that says "Patch Gcc-2.95.3 to 2.95.4 (prerelease) for
> VxWorks-PPc.", what file you get depends on where on the link you click.
> You have to find the right spot to get the PPC patch and not the Altivec
> patch.
> 

Thanks for the cautionary note. I must have clicked on the right
spot the first time. I did get the right file. Just for good measure
I also did download the Altivec patch as well.

I did the patch with the: vx-ppc-gcc.diff file
and then compiled without any problems, up to the unnecessary
libiberty point.

> Also, I got bitten by the "You need to install autogen" issue described
> on the FAQ/Docs page. But using the "inclhack.sh.diff" patch doesn't fix
> things. Something about the end_else_label sed script is wrong:
> 
>     Fixing directory /usr/include into
> /home/smagnani/xyzzy/build/gcc-2.95.3/gcc/fixinc
>     Checking header files
>     sed: -e expression #1, char 252: Invalid preceding regular
> expression
>     Fixed ./ss/ss.h:
>           end_else_label
> 
> I tried gutting the End_Else_Label code in fixinc.sh, substituting "cat"
> for "sed" (i.e. turn the End_Else_Label fixup into a no-op). That at
> least seems to have allowed the build to complete. I'm not sure what
> side-effects there might be.
> 

I wasn't sure about the autogen stuff, so I ignored that step. 
My build did complete up to the:

fdmatch.c:59: storage size of `sbuf1' isn't known
fdmatch.c:60: storage size of `sbuf2' isn't known
make[1]: *** [fdmatch.o] Error 1
make[1]: Leaving directory 
`/usr/local/src/gcc-2.95.3/powerpc-wrs-vxworks/libiberty'
make: *** [all-target-libiberty] Error 2

errors which apparently signal a completed build.
I see though that one comment on the FAQs/Doc where the way
I did it may result in:

->output, but that isnt obvious. This lead to the xgcc being built
->without the fixed headers for varargs. It may be useful to make that
->clear in the FAQs? The business of fixinc is cryptic enough already!

...again i'm ignorant as to if the above will affect me.

Next week I'll see if the compiler actually compiles 
code that the MPC750 can understand. If I run into trouble
I'll try redoing it with the autogen.
  
Thanks for your advice!

Jim 



------
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]