NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: misc/39454: UPDATE build of amd64 bootcd fails to pick up new kernel



The following reply was made to PR misc/39454; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: misc-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost
Subject: Re: misc/39454: UPDATE build of amd64 bootcd fails to pick up new 
kernel
Date: Wed, 3 Sep 2008 16:39:42 +0200

 On Wed, Sep 03, 2008 at 02:30:00PM +0000, he%NetBSD.org@localhost wrote:
 > >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
 
 I think the right target for this would be "iso_image" and not "dependall".
 This is typically done after dependall have been run though the whole tree.
 
 
 > [...]
 >      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...
 
 'build.sh release' will build a release, including binary sets and INSTALL
 kernel with embeded ramdisk.
 'build.sh iso-image' will take whatever exists in the sets directory and
 build a cd image with it. It won't try to update kernels or binaries.
 
 -- 
 Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
      NetBSD: 26 ans d'experience feront toujours la difference
 --
 


Home | Main Index | Thread Index | Old Index