Re: Unsuccessful build of a cross PowerPC GCC 2.95.x for an Intel

[Geoff Keating <geoffk at ozemail dot com dot au>]

greyham@research.canon.com.au (Graham Stoney) writes:

> Patrick Lerda writes:
> > #!/bin/sh
> > CFLAGS=-O6 CXXFLAGS=-O6 /usr/src/gcc-2.95/configure --prefix=/usr \
> > --host=i586-unknown-linux --build=i586-unknown-linux \
> > --target=powerpc-unknown-linux \
> > --with-cpu=603e \
> > --with-headers="/usr/powerpc-unknown-linux/include" \
> > --with-libs="/usr/powerpc-unknown-linux/lib"
> > 
> > make cross
> > 
> > 
> > ...
> > 
> > After a while the process fail in the directory libiberty, an entry is
> > missing in the Makefile.
> 
> Well don't keep us in suspense; what error message do you get when it fails,
> and which entry in the Makefile do you think is missing?
> 
> I've successfully built powerpc-linux crosses with both 2.95 and 2.95.1 on i586
> using glibc-2.1.2pre2 as my runtime library. If you're using gcc 2.95, try
> 2.95.1.

I see this too for 2.95.1, from sparc-solaris.  I have all the right
files in /usr/local/powerpc-unknown-linux-gnu: cross-binutils, shared
libraries, header files.  I did a straight 
'configure --target=powerpc-unknown-linux-gnu', and it built fine until:

make[1]: Entering directory `/sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/powerpc-unknown-linux-gnu/libiberty'
test x"no" != xyes || \
  /sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/gcc/xgcc -B/sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/gcc/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c -DHAVE_CONFIG_H -g -O2 -I. -I/home/geoffk/co/gcc-2.95.1/libiberty/../include   /home/geoffk/co/gcc-2.95.1/libiberty/choose-temp.c -o pic/choose-temp.o
/sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/gcc/xgcc -B/sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/gcc/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c -DHAVE_CONFIG_H -g -O2 -I. -I/home/geoffk/co/gcc-2.95.1/libiberty/../include  /home/geoffk/co/gcc-2.95.1/libiberty/choose-temp.c
/home/geoffk/co/gcc-2.95.1/libiberty/choose-temp.c:29: stdio.h: No such file or directory
/home/geoffk/co/gcc-2.95.1/libiberty/choose-temp.c:30: sys/types.h: No such file or directory
make[1]: *** [choose-temp.o] Error 1

This is not particularly surprising, because using -v produces the
following output from cpp:

GNU CPP version 2.95.1 19990816 (release) (PowerPC GNU/Linux)
#include "..." search starts here:
#include <...> search starts here:
 .
 /home/geoffk/co/gcc-2.95.1/libiberty/../include
 /sloth/disk1/build/gcc-2.95.1/H-sparc-sun-solaris/T-powerpc-unknown-linux-gnu/gcc/include
End of search list.
The following default directories have been omitted from the search path:
 /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.1/../../../../include/g++-3
 /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.1/include
 /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.1/../../../../powerpc-unknown-linux-gnu/sys-include
 /usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.1/../../../../powerpc-unknown-linux-gnu/include
End of omitted list.

and since it's omitting all the /usr/local directories, it sees no
header files.  This directly contradicts the documentation which says
that you can put your headers in the right places and it will Just
Work.

-- 
Geoffrey Keating <geoffk@cygnus.com>