NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
misc/39454: UPDATE build of amd64 bootcd fails to pick up new kernel
>Number: 39454
>Category: misc
>Synopsis: UPDATE build of amd64 bootcd fails to pick up new kernel
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: misc-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Sep 03 14:30:00 +0000 2008
>Originator: Havard Eidnes
>Release: NetBSD 4.99.72
>Organization:
I try...
>Environment:
System: Target: amd64 4.99.72 -current as of yesterday
Architecture: amd64
Machine: amd64
>Description:
I'm trying to fix bugs preventing the installation of NetBSD
on a HP ProLiant BL460c G1 system, using the amd64 port.
This system typically wants an ISO image to boot from.
I'm trying to use the in-tree methods to replicate the parts
of the build which is creating the boot.iso image, but for
some reason that I can't seem to fathom, I appear to be unable
to make the build work as intended.
I've found distrib/amd64/cdrom/bootcd/, which appears to
describe the build procedure used. However, doing an UPDATE
build using "nbmake-amd64" in distrib/amd64/, the build
creates the new ramdisk and the new netbsd-INSTALL.gz file,
but the build in cdroms/bootcd/ etc. fail to pick up the new
kernel and do not appear to do any work. Also, doing
"nbmake-amd64 release" does not install the new (or old) iso
images. Here's excerpts of the build log:
quattro: {108} /u/build/HEAD/tools/amd64/bin/nbmake-amd64 dependall
dependall ===> ramdisks
dependall ===> ramdisks/ramdisk
`cat.ro' is up to date.
`chmod.ro' is up to date.
`cp.ro' is up to date.
`dd.ro' is up to date.
`df.ro' is up to date.
`ed.ro' is up to date.
`ln.ro' is up to date.
...
depend ===> ramdisks/ramdisk/mbr
`fdisk.ro' is up to date.
`fsck.ro' is up to date.
`fsck_ffs.ro' is up to date.
...
`rtsol.ro' is up to date.
link ramdisk/ramdiskbin
strip ramdiskbin
build ramdisk/work
missing: ./bin (created)
missing: ./dev (created)
...
missing: ./var/spool/lock (created)
create ramdisk/ramdisk.fs
Calculated size of `ramdisk.fs.tmp': 5120000 bytes, 60 inodes
Extent size set to 4096
ramdisk.fs.tmp: 4.9MB (10000 sectors) block size 4096, fragment size 512
using 1 cylinder groups of 4.88MB, 1250 blks, 64 inodes.
super-block backups (for fsck -b #) at:
32,
Populating `ramdisk.fs.tmp'
Image `ramdisk.fs.tmp' complete
dependall ===> instkernel
create instkernel/netbsd-INSTALL (from:
/u/build/HEAD/obj/amd64/sys/arch/amd64/compile/INSTALL/netbsd
/u/build/HEAD/obj/amd64/distrib/amd64/ramdisks/ramdisk/ramdisk.fs)
got symbols from netbsd-INSTALL.tmp
mapped netbsd-INSTALL.tmp
copying image /u/build/HEAD/obj/amd64/distrib/amd64/ramdisks/ramdisk/ramdisk.fs
into netbsd-INSTALL.tmp
done copying image
exiting
create instkernel/netbsd-INSTALL.gz
...
dependall ===> cdroms
dependall ===> cdroms/bootcd
dependall ===> cdroms/bootcd-com
dependall ===> cdroms/installcd
dependall ===> floppies
dependall ===> floppies/bootfloppy
create bootfloppy/netbsd (from:
/u/build/HEAD/obj/amd64/distrib/amd64/instkernel/netbsd-INSTALL.gz)
create bootfloppy/boot1.fs (from: boot
/u/build/HEAD/src/distrib/amd64/floppies/common/boot.cfg netbsd)
pax: Removing leading / from absolute path names in the archive
Running instboot: /u/build/HEAD/tools/amd64/bin/nbinstallboot -mamd64
floppy.11754.tar /u/build/HEAD/dest/amd64/usr/mdec/bootxx_ustarfs
Free space in last tar block: boot 268,
/u/build/HEAD/src/distrib/amd64/floppies/common/boot.cfg 46, netbsd 307,
Writing 5603328 bytes (5472 KB) on 4 disks, free space 270336 bytes (264 KB)
Creating disk 1 to boot1.fs
Creating disk 2 to boot2.fs
Creating disk 3 to boot3.fs
Creating disk 4 to boot4.fs
Final result:
-rw-r--r-- 1 he wheel 1474560 Sep 3 16:18 boot1.fs
-rw-r--r-- 1 he wheel 1474560 Sep 3 16:18 boot2.fs
-rw-r--r-- 1 he wheel 1474560 Sep 3 16:18 boot3.fs
-rw-r--r-- 1 he wheel 1204224 Sep 3 16:18 boot4.fs
You'll note that it dutifully created the new boot floppies,
but alas, no new bootcd iso image.
Doing "nbmake-amd64 prepare" in cdroms/bootcd/ does indeed
copy in the new netbsd INSTALL kernel to the OBJDIR, but
if I thereafter do an "nbmake-amd64 dependall" in the same
directory, nothing is done (no new iso image is created).
I smell a missing dependency tracking allowing UPDATE builds
to work as intended.
I'm also somewhat surprised that there's no top-level target
to build.sh to create the boot images; the iso-image target
from build.sh bundles up the RELEASEDIR contents, and does not
pick up the new INSTALL kernel I just built...
>How-To-Repeat:
See above.
>Fix:
Sorry, this appears to be above what I'm able to figure out.
Home |
Main Index |
Thread Index |
Old Index