problem building 64-bit gcc

[Dan Kegel]

Alan Modra wrote:
> On Wed, Apr 28, 2004 at 04:41:26PM -0400, Chris Friesen wrote:
>
>>config/rs6000/linux64.h:588:20: signal.h: No such file or directory
>>config/rs6000/linux64.h:590:26: sys/ucontext.h: No such file or directory
>
>
> There are various ways of overcoming the circular dependency between
> glibc and gcc.  Probably the best one with current glibc sources is
> to configure glibc and run "make install-headers" before building
> gcc.  Last time I checked, this didn't quite work, and I found I needed
> to create a dummy gnu/stubs.h.  Bootstrapping tools from scratch is
> still a pain..

Yup.  That's why I wrote (and more or less maintain) crosstool.
http://kegel.com/crosstool/crosstool-0.28-rc8.tar.gz seems to build
gcc-3.4.0/glibc-2.3.2 powerpc64 ok finally.
Say, could somebody here give it a try?  Here's how:

wget http://kegel.com/crosstool/crosstool-0.28-rc8.tar.gz
tar -xzvf crosstool-0.28-rc8.tar.gz
cd crosstool-0.28-rc8
lynx doc/crosstool-howto.html
sudo mkdir /opt/crosstool
sudo chown $USER /opt/crosstool
sh demo-powerpc64.sh

That should create a good toolchain (assuming the config file
from linux-2.6.5's allnoconfig suffices; otherwise replace the
sample config file linuxppc64.config).  The path to the compiler would be
/opt/crosstool/powerpc64-unknown-linux-gnu/gcc-3.4.0-glibc-2.3.2/bin/powerpc64-unknown-linux-gnu-gcc
- Dan

--

** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/