This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
No Subject
I copied the headers from my previous gcc-2.7.2.2 build, and I got past
this part (but see below). But if I had been building a cross compiler
for the first time, what should I have done? Copied the native system
headers? Copied the headers from the newlib distribution? (BTW, I did
specify --with-newlib) I'd like to see this clarified a bit in the FAQ
or the installation notes.
Even worse is --with-libs. If this was a virgin build, where would I
get libraries? For that matter, would my gcc-2.7.2.2-compiled libraries
even be compatible? I left it off for now.
I don't know if it's related, but now the build is dying with the
following (pathnames shortened by me for readability):
------------------
gmake[4]: Leaving directory `/[...]/m68k-elf/msoft-float/libiberty'
gmake[3]: Leaving directory `/[...]/m68k-elf/libiberty'
gmake[2]: Leaving directory `/[...]/m68k-elf/libiberty'
gmake[2]: Entering directory `/[...]/m68k-elf/libio'
gmake[2]: *** No rule to make target `all'. Stop.
gmake[2]: Leaving directory `/[...]/m68k-elf/libio'
gmake[1]: *** [all-target-libio] Error 1
gmake[1]: Leaving directory `/[...]/build-m68k'
gmake: *** [cross] Error 1
------------------
Is there a bug in the config script? There was a Makefile in libio/,
but no rule I could see for "all".
--
John A. Breen
jab3@hotmail.com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com