trying to emerge system, and it failed here:
cdimage / # emerge system
Calculating system dependencies ...done!
>>> emerge (1 of 65) sys-libs/gdbm-1.8.0-r5 to /
>>> md5 ;-) gdbm-1.8.0.tar.gz
>>> Unpacking source...
>>> Unpacking gdbm-1.8.0.tar.gz to /var/tmp/portage/gdbm-1.8.0-r5/work
patching file gdbm-1.8.0/gdbm.info
>>> Source unpacked.
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc -march=2.0 -O3 -pipe -mschedule=8000 )
works... yes
checking whether the C compiler (gcc -march=2.0 -O3 -pipe -mschedule=8000 ) is a
cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for a BSD compatible install... /bin/install -c
checking host system type... Invalid configuration `hppa2.0-unknown-linux-gnu':
machine `hppa2.0-unknown' not recognized
checking for ranlib... ranlib
checking for ld used by GCC...
/usr/lib/gcc-lib/hppa2.0-unknown-linux-gnu/3.2.2/../../../../hppa2.0-unknown-linux-gnu/bin/ld
checking if the linker
(/usr/lib/gcc-lib/hppa2.0-unknown-linux-gnu/3.2.2/../../../../hppa2.0-unknown-linux-gnu/bin/ld)
is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
!!! ERROR: sys-libs/gdbm-1.8.0-r5 failed.
!!! Function src_compile, Line 37, Exitcode 1
!!! (no error message)
Reproducible: Always
Steps to Reproduce:
1. boot liveCD on HPPA 2.0 system
2. emerge system
3.
Actual Results:
THe build of gdbm failes (due to ltconfig, it looks like)
Expected Results:
uhhhhh accepted a valid machine type?
I am going to switch to an older type, like hppa1.1. Since I have a D370, I
*should* be using hppa2.0, but it dosen't matter *that* much. It would make the
build process correct to accept valid machine types.
interestingly, changing *only* the machinetype to hppa1.1, but leaving the
CFLAGS set to "-m2.0 -O2 -schedule=8000" still worked. Therefore, I am
thinking that ltconfig/autoconf/whatever is having trouble with this machine
type. perhaps masking the 2.0 machinetype in the ebuild would solve this...
