Re: Debian installer image for Debian/m68k

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/06/2017 03:36 AM, Finn Thain wrote: > I see there is code to copy some files that don't exist in any debian > package. This code should be copying macbinary files, not hqx or hfs > files. That is why I sent you those macbinary files to add to m68kboot. > (Please refer to email messages of

Re: Debian installer image for Debian/m68k

2017-10-05 Thread Finn Thain
On Fri, 6 Oct 2017, John Paul Adrian Glaubitz wrote: > > The code to handle Penguin is still present in debian-installer [1] and > for it to work, I just need to make sure Penguin is available in Debian > again. [...] > I see there is code to copy some files that don't exist in any debian pa

Re: Debian installer image for Debian/m68k

2017-10-05 Thread John Paul Adrian Glaubitz
On 09/01/2017 10:51 AM, Finn Thain wrote: > The Debian 3 m68k installer ISO mounts under System 7, which is helpful. > On it you can find the Penguin bootloader, in Binhex encoded form: > > install/mac/Penguin.doc.hqx > install/mac/Penguin-19.hqx > install/mac/Penguin-Colors.hqx > > The etch-m68

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/05/2017 11:49 PM, Christoph Biedl wrote: > About that particular issue I'd really like to avoid a per-architecture > switch in busybox. It adds complexity and works around a problem > instead of solving it. I wouldn't call that simple if-clause complexity. > So please take this to gcc first

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread Christoph Biedl
Steve McIntyre wrote... > On Thu, Oct 05, 2017 at 06:12:46PM +0200, John Paul Adrian Glaubitz wrote: > >Hmm, ok. Is that currently actually a concern? If I'm seeing that correctly, > >the "-Os" here only saved us around 200k. Does that already make a difference > >on armel? > > Massively so, yes.

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/05/2017 06:38 PM, Steve McIntyre wrote: >> On second thought, I would actually recommended to revert this change >> for all architectures. Size isn't so much a constraint anymore these >> days, you reduce the binary by about 200k. I don't think this is worth >> the risk of breaking something

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread Steve McIntyre
On Thu, Oct 05, 2017 at 06:12:46PM +0200, John Paul Adrian Glaubitz wrote: >On 10/05/2017 05:55 PM, Roger Shimizu wrote: >> > On second thought, I would actually recommended to revert this change >> > for all architectures. Size isn't so much a constraint anymore these >> > days, you reduce the bin

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread Steve McIntyre
On Thu, Oct 05, 2017 at 09:25:12AM +0200, John Paul Adrian Glaubitz wrote: >Hi! > >On 10/05/2017 01:16 AM, John Paul Adrian Glaubitz wrote: >> Since busybox is very important to boot the system and get >> debian-installer working, I would like to ask to have the >> change from [1] reverted for m68k

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/05/2017 05:55 PM, Roger Shimizu wrote: On second thought, I would actually recommended to revert this change for all architectures. Size isn't so much a constraint anymore these days, you reduce the binary by about 200k. I don't think this is worth the risk of breaking something as fundeman

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread Roger Shimizu
On Thu, Oct 5, 2017 at 4:25 PM, John Paul Adrian Glaubitz wrote: > Hi! > > On 10/05/2017 01:16 AM, John Paul Adrian Glaubitz wrote: >> >> Since busybox is very important to boot the system and get >> debian-installer working, I would like to ask to have the >> change from [1] reverted for m68k unt

Re: Installing with new Installer-Image

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/05/2017 04:19 PM, Stefan Niestegge wrote: Hi i just tried the CD, and after modprobing pata_falcon it found the CD and setup can be tried. Will report my progress! Great. Let me know when you run into any issues. Note that after installation finishes, you need to copy the kernel and init

Re: Installing with new Installer-Image

2017-10-05 Thread Stefan Niestegge
Ok, this turned out to be a problem with busybox, see [1]. Installation on Aranym (and hence on a real Atari) works now. - Use image:   - https://cdimage.debian.org/cdimage/ports/9.0/m68k/iso-cd/debian-9.0-m68k-NETINST-1.iso - Use kernel and initrd from the image or grab those here:   -

Re: Installing with new Installer-Image

2017-10-05 Thread John Paul Adrian Glaubitz
On 10/04/2017 06:34 PM, John Paul Adrian Glaubitz wrote: On 10/04/2017 03:30 PM, John Paul Adrian Glaubitz wrote: There is an updated debian-installer image available now for m68k which should finally fix the driver issue for Atari [1]. I have just tried it myself on both Aranym and qemu-m68k.

Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

2017-10-05 Thread John Paul Adrian Glaubitz
Hi! On 10/05/2017 01:16 AM, John Paul Adrian Glaubitz wrote: Since busybox is very important to boot the system and get debian-installer working, I would like to ask to have the change from [1] reverted for m68k until we have fixed the potential bug in gcc which most likely mis-compiled busybox.