Trouble building GCC 2.95.2 on intel Linux as cross compiler for PPC

[Jeffrey A Law]

  In message < 200007120800.BAA03691@homer.ka9q.ampr.org >you write:
  > >You're missing newlib.
  > 
  > Thanks. I didn't initially install newlib because I only needed the
  > cross-compiler to look at the assembler code generated for some source
  > code I'm tuning.
  > 
  > Following your suggestion, I tried building all three packages
  > (binutils, gcc, newlib) sequentially according to the instructions in
  > 
  > http://www.objsw.com/CrossGCC/FAQ-4.html .
  > 
  > That didn't work because of an apparent circular dependency between
  > gcc and newlib that only appears when building gcc as a cross
  > compiler. Building gcc needs newlib to be installed first and building
  > newlib needs the gcc cross-compiler to be installed first.
Hmm, then there must be something wrong in those instructions.  I build
this almost daily.  Oh, wait, maybe you're not using a single source tree...


  > I finally succeeded by merging the gcc, binutils and newlib trees into
  > a single source tree as described later in that same web page. I had
  > to do the merging manually as the one-tree script provided didn't seem
  > to work on the latest versions of the packages.
Yup.  This is the way to go.


  > I suggest that a merged tarball of the three source trees (the latest
  > versions of binutils, gcc & newlib) be made available on the FTP
  > mirror sites for those who wish to build cross compilers. That sure
  > would have been much easier and less confusing for me.
The GNU project has always been very much against doing that kind of thing;
what we are considering is having everything in a single CVS repository
so that people can set up their one tree build systems easily.

  > Thanks again for the help!
No problem.  The least I could do after using your ka9q package 10 years ago.


jeff