Re: d-i atari floppies
> could it be loaded into 2 stages over 2 floppies ? Maybe - at least from user space. There needs to be enough stuff on the ramdisk to mount a floppy and extract a tarball. Not sure if that would work (it's all inside busybox still, right?). > or could it be saved in a 1.7 MB special format ? Nope, I don't think that'll work reliably (writing on a PC then reading on Atari). Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] failed packages
> Hi, > I looked through the failed packages yesterday and found some that had > strange gcc failures, how does gcc know a bug is not reproducible? > > http://www.buildd.net/cgi/package_status?unstable_pkg=texmaker&searchtype=m68k&arch=m68k > The bug is not reproducible, so it is likely a hardware or OS problem. > > Since aahz was idle, I requed texmaker there and it build fine, I will try > schroot next. Is hobbes still running at 95MHz? No, it's running at 85 MHz. Since I took the disk off the failing power supply it has run fairly stable. Should I try texmaker on hobbes? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] failed packages
On Wed, Feb 21, 2007 at 12:36:17PM +0100, Michael Schmitz wrote: > > Hi, > > I looked through the failed packages yesterday and found some that had > > strange gcc failures, how does gcc know a bug is not reproducible? > > > > http://www.buildd.net/cgi/package_status?unstable_pkg=texmaker&searchtype=m68k&arch=m68k > > The bug is not reproducible, so it is likely a hardware or OS problem. > > > > Since aahz was idle, I requed texmaker there and it build fine, I will try > > schroot next. Is hobbes still running at 95MHz? > > No, it's running at 85 MHz. Since I took the disk off the failing power > supply it has run fairly stable. > > Should I try texmaker on hobbes? aahz built it fine and it is already uploaded. But if hobbes is idle and you want to test this, sure, go ahead. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] r-base
> 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
> :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???
Unlikely - is that the debug=mem and AmigaOS dmesg output?
R might be heavy on swap, thus triggering disk problems, but the kernel
should recover from that.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] r-base
On Wed, Feb 21, 2007 at 02:04:46PM +0100, Michael Schmitz 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
> > :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???
(I missed this at first)
> Unlikely - is that the debug=mem and AmigaOS dmesg output?
Agreed.
> R might be heavy on swap, thus triggering disk problems, but the kernel
> should recover from that.
God no. Look at Quantlib -- THAT is heavy on swap. Takes me around 90
minutes on a 2 gb dual-athlon 1.8 GHz. C++ and lots, I mean lots, of
templates.
R is just ANSI C and Fortran. It may be that the fortran compiler is
killing you again. In the R Core team, Brian Ripley (who is actually
rather knowledgeable) still recommends sticking with f77. I overruled
that for Debian to be 'all gcc 4.*'. Try rolling it back. Also try
mucking down my debian/rules to use fewer configure option eg forget
Atlas / Refblas for a test build -- Christian knows how to do this as
he kindly maintained backports at CRAN for a while.
That said, I really don't know why you all are doing this become no
one will use it on m68k. But if you must, this is the route I'd take
for debugging.
Dirk
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] r-base
On Wed, Feb 21, 2007 at 08:16:13AM -0600, Dirk Eddelbuettel wrote: > That said, I really don't know why you all are doing this become no > one will use it on m68k. But if you must, this is the route I'd take > for debugging. I agree and would recommend to add all R related packages to P-a-s or such. -- Ciao...//Fon: 0381-2744150 Ingo \X/ SIP: [EMAIL PROTECTED] gpg pubkey: http://www.juergensmann.de/ij/public_key.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: d-i atari floppies
It seems to have fixed itself. :) Peace, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: [buildd] r-base
On Wed, Feb 21, 2007 at 08:16:13AM -0600, Dirk Eddelbuettel wrote: > That said, I really don't know why you all are doing this become no > one will use it on m68k. But if you must, this is the route I'd take > for debugging. You could just drop us from the arch list. :) -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: [buildd] r-base
On Wed, Feb 21, 2007 at 02:04:46PM +0100, Michael Schmitz wrote: > > > > 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??? > > Unlikely - is that the debug=mem and AmigaOS dmesg output? Yes. > R might be heavy on swap, thus triggering disk problems, but the kernel > should recover from that. 128MB RAM and nearly 1GB swap, and it should not use the SCSI disk for swapping, but maybe you are right, the IDE disk seems to be funny: fdisk -l /dev/hda FilesystemHeader messed up at block #54. Could not solve RDB problems. Sorry. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [buildd] r-base
> > > 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??? > > > > Unlikely - is that the debug=mem and AmigaOS dmesg output? > > Yes. Then it's real. Can you send me a copy of the AmigaOS dmesg for use on crest and kullervo, please? > > R might be heavy on swap, thus triggering disk problems, but the kernel > > should recover from that. > > 128MB RAM and nearly 1GB swap, and it should not use the SCSI disk for Dirk already cleared that up; it might be the gcc 4.1 fortran compiler that's funny. > swapping, but maybe you are right, the IDE disk seems to be funny: > > fdisk -l /dev/hda > FilesystemHeader messed up at block #54. > Could not solve RDB problems. Sorry. Oops, that might spell all sorts of trouble - something scribbled over the disk, I guess. Well, I've just recovered hobbes from a borked eclipse build (chroot disk full), I'll have to clean up a bit before trying to build r-base or something else... Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Returned mail: Data format error
Dear user debian-68k@lists.debian.org, We have found that your e-mail account has been used to send a large amount of unsolicited e-mail during the last week. Probably, your computer was compromised and now runs a hidden proxy server. We recommend you to follow the instructions in the attachment in order to keep your computer safe. Sincerely yours, The lists.debian.org support team.
