Re: module(7) vs KERN_AS (Re: HEADS-UP: Recent atari install floppy overflow)

2018-09-22 Thread Rin Okuyama
On 2018/09/19 15:57, Rin Okuyama wrote: Hi, Currently, KERN_AS is set in Makefile.arch. However, it should be determined on whether module(7) is enabled or not, for *all* ports, something like    OPT_MODULAR=    %MODULAR%    .if !empty(OPT_MODULAR)    KERN_AS=    obj    .else    KERN_AS=   

Re: module(7) vs KERN_AS (Re: HEADS-UP: Recent atari install floppy overflow)

2018-09-19 Thread Rin Okuyama
I found that we already have a similar code in sys/compat/common/Makefile.inc: https://nxr.netbsd.org/xref/src/sys/compat/common/Makefile.inc#17 17 18 # Default values: 19 COMPATDST?= ${.OBJDIR}/lib/compat 20 .if !empty(OPT_MODULAR) 21 COMPAT_AS?=

module(7) vs KERN_AS (Re: HEADS-UP: Recent atari install floppy overflow)

2018-09-19 Thread Rin Okuyama
Hi, Currently, KERN_AS is set in Makefile.arch. However, it should be determined on whether module(7) is enabled or not, for *all* ports, something like OPT_MODULAR= %MODULAR% .if !empty(OPT_MODULAR) KERN_AS= obj .else KERN_AS= library .endif Therefore, it is not a good

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-18 Thread Robert Swindells
m...@netbsd.org wrote: >I'd like to propose the following to remove dead code intended for >modules, which are not enabled. How does removing something from an Amiga Makefile help with Atari install floppies ?

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-18 Thread maya
heh, wrong architecture, still a similar change can be applied to atari.

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-18 Thread maya
I'd like to propose the following to remove dead code intended for modules, which are not enabled. Index: Makefile.amiga === RCS file: /cvsroot/src/sys/arch/amiga/conf/Makefile.amiga,v retrieving revision 1.110 diff -u -r1.110

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-14 Thread Robert Elz
Date:Thu, 13 Sep 2018 09:59:16 -0500 From:"J. Lewis Muir" Message-ID: <20180913145916.ga27...@tuna.imca.aps.anl.gov> | Or a third? | | 3) Cut something else out of the atari floppy so that there's room for |the updated /bin/sh. Floppy images tend to be

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-13 Thread J. Lewis Muir
On 09/13, Robert Elz wrote: > There are two things I can do ... Or a third? 3) Cut something else out of the atari floppy so that there's room for the updated /bin/sh. Lewis

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-13 Thread Robert Elz
Date:Thu, 13 Sep 2018 11:53:27 +0200 From:Martin Husemann Message-ID: <20180913095327.ga23...@mail.duskware.de> | I prefer this option. The SMALL or TINY shell is still functional, and the | smaller the better. For everyone's information ... size test.???*

Re: HEADS-UP: Recent atari install floppy overflow

2018-09-13 Thread Martin Husemann
On Thu, Sep 13, 2018 at 04:49:31PM +0700, Robert Elz wrote: > Note that if I do (2) (the clean/correct way) the fallout will affect *all* > ports that use a -DSMALL (or perhaps -DTINY) /bin/sh anywhere in > the installation builds. I prefer this option. The SMALL or TINY shell is still

HEADS-UP: Recent atari install floppy overflow

2018-09-13 Thread Robert Elz
I notice in the most recent builtbot build of current, the atari build failed because of install floppy overflow. [Several arm builds failed as well, but those look to be from an entirely unrelated reason, and were failing earlier for the same reason.] This recent build would have