Subject: port-i386/19018: i386 floppies build scripts should not use mk.conf
To: None <>
From: Matthew Mondor <>
List: netbsd-bugs
Date: 11/11/2002 23:51:28
>Number:         19018
>Category:       port-i386
>Synopsis:       i386 floppies build scripts should not use mk.conf
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 11 20:52:01 PST 2002
>Originator:     Matthew Mondor
>Release:        NetBSD 1.6
 On i386 port (perhaps a similar situation exists on other ports) there are
 several compiler optimization flags which can be used, i.e. to generate code
 for i486, i586 or i686. On some systems this makes quite a difference.
 The current NetBSD 1.6 build scripts seem to take into account /etc/mk.conf
 flags when building floppies, which can cause the system build to fail
 (filesystem full). 1.5 release was also subject to this problem. This causes
 the administrator to have to complete the rest of the steps manually, and
 could cause problems (especially if a step is skipped). A notable problem
 would be attempting to upgrade a system with a set missing the obsolete or
 transition files list.
 Build a complete release(7) set using the NetBSD 1.6 sources, using either of
 these in /etc/mk.conf:
  CFLAGS='-march=i586 -O2 -fexpensive-optimizations -pipe'
  CFLAGS='-march=i686 -O2 -fexpensive-optimizations -pipe'
 The build scripts should not take into account /etc/mk.conf CFLAGS|COPTS
 nor take into consideration environmental $CFLAGS, when building floppy
 binaries before using vnd to create them. As a result standard i386 ones
 would still remain.