Re: [buildd] r-base
On 19 February 2007 at 18:48, Christian T. Steigies wrote:
| 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
Yes, we had similar cases in the past. Fortran on m68k has its charms.
You may want to switch back to f2c (but I'd hate to roll that through all
dependents of R :-/) or manually descent via -O2, -O1, -O0. That helpd in the
past.
| 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,
I didn't know. Not pretty.
Would you all consider a exemption for the whole R complex? I don't have
time (or inclination) to fix this. Let's just not build this and move on.
| but it is kind of a nuisance. If you have an idea how to make R work on m68k
| again, please let us know.
I honestly do not.
The best of R Core;s knowledge is in the 'R Admin + Inst' manual in
r-base-(html,pdf), the R sources (in doc/manual/) and on the website.
I have no time to carry this upstream, nor would I expect much useful from R
Core as nobody is using m68k around there.
If you as a porter want to contact them, please feel free. You can reach R
Core as r-core@r-project.org. I am sure they'd try help where they can, but
if the toolchain is busted, the kernel is busted, ...
Dirk
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
Reply to: