[buildd] r-base

["Christian T. Steigies" <cts@debian.org>]

Hi,
I tried to build r-base on aahz, it got a bit further than kullervo.
kullervo failed with an ICE:

gcc     -I. -I../../src/include -I../../src/include  -DHAVE_CONFIG_H   -fpic
-std=gnu99 -O3 -pipe -c vfonts.c -o vfonts.o
gfortran  -fpic  -O3 -pipe -c xxxpr.f -o xxxpr.o
<built-in>:0: internal compiler error: Segmentation fault

ahhz built that fine, but a little later the whole machine froze:

building package 'base'
mkdir -p -- ../../../library/base/demo
mkdir -p -- ../../../library/base/po
mkdir -p -- ../../../library/base/man

I guess the command that made the machine freeze is not shown here.
This is from dmesg on aahz, lots of NETDEV, some hda and lots of eps0
messages after that:

NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
hda: status timeout: status=0xff { Busy }
ide: failed opcode was: unknown
hda: drive not ready for command
ide0(?): unexpected interrupt, status=0xff, count=1
esp0: Gross error sreg=7f
esp0: No current cmd during gross error, resetting bus
esp0: Resetting scsi bus
esp0: Gross error sreg=7f
esp0: No current cmd during gross error, resetting bus
esp0: Resetting scsi bus

The system is install on hda, the SCSI disk is not used for building, maybe
I should disconnect it? Can R be responsible for SCSI or IDE errors???

aahz has a newer libc6 and kernel-headers installed than kullervo

kullervo:
Toolchain package versions: libc6-dev_2.3.6.ds1-4
linux-kernel-headers_2.6.18-1 gcc-4.1_4.1.1-21 g++-4.1_4.1.1-21
binutils_2.17-3 libstdc++6-4.1-dev_4.1.1-21 libstdc++6_4.1.1-21

aahz:
Toolchain package versions: libc6-dev_2.3.6.ds1-11
linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.1-21 g++-4.1_4.1.1-21
binutils_2.17-3 libstdc++6-4.1-dev_4.1.1-21 libstdc++6_4.1.1-21

I am wondering if there is a way to try and continue this build, or if we
should give it another shot on a different machine?

Dirk, R is in pretty bad shape on m68k, in case you do not know. All
packages that depend on R make m68k machines freeze while they try to
install R. And current R does not build on m68k... not that anybody cares,
but it is kind of a nuisance. If you have an idea how to make R work on m68k
again, please let us know.

Christian