Skip to contentSkip to conversation

Toolchain testing.

parisc-linux Carlos O'Donell 1 participant 2 messages Jul 17, 2002

lore
Share & tools
lore
#0 lore raw

Parisc,

Started testing toolchain builds using some of the new scripts I'm building for 'cross-check' ... right off the bat, the first toolchain test permuation doesn't work :)

Toolchain Test 1:

Crossing from hppa -> hppa64

Using:

Reading specs from /usr/lib/gcc-lib/hppa-linux/3.0.4/specs
Configured with: ../src/configure -v --enable-languages=c,c++,f77,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --with-cpp-install-dir=bin --enable-objc-gc hppa-linux Thread model: posix
gcc version 3.0.4

GNU ld version 2.12.90.0.1 20020307 Debian/GNU Linux Supported emulations:
hppalinux
hppa64linux

Uses debianized binutils/gcc/glibc from 'testing' for HPPA.

binutils - binutils-2.12.90.0.1
gcc - gcc-3.0-3.0.4ds3
glibc - glibc_2.2.5-7

Binutils builds/installs ok.

GNU ld version 2.12.90.0.1 20020307 Debian/GNU Linux
Supported emulations:
hppa64linux

Unfortunately gcc dies while compiling gengenrtl.c ... looks like something didn't get #define'd properly.

Attached is the build.log (and -E). If anyone has any idea why it croaks, and what might be missing? I've been scratching my head most of the evening... :}

c.
---

Note:
I have modified the control files for all three pieces of the toolchain. This was done with extreme care. The three pieces of the toolchain now allow for much finer-grained compile time options that can be eventually set by dpkg-buildpackage (or a magical dpkg-compile... or an enhanced dpkg-architecture ... or whatever)

#1 lore raw
Quoted 9 lines

Note:
I have modified the control files for all three pieces of the toolchain. This was done with extreme care. The three pieces of the toolchain now allow for much finer-grained compile time options that can be eventually set by dpkg-buildpackage (or a magical dpkg-compile... or an enhanced dpkg-architecture ... or whatever)

Another note, I have looked at dpkg-cross.

c.