netbsd-bugs@netbsd.org
[Top] [All Lists]

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

Subject: Re: misc/39454: UPDATE build of amd64 bootcd fails to pick up new kernel
From: Manuel Bouyer
Date: Wed, 03 Sep 2008 19:20:13 UTC
Newsgroups: fa.netbsd.bugs

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

From: Manuel Bouyer <bouyer@xxxxxxxxxxxxxxx>
To: Havard Eidnes <he@xxxxxxxxxx>
Cc: gnats-bugs@xxxxxxxxxx, misc-bug-people@xxxxxxxxxx, gnats-admin@xxxxxxxxxx,
        netbsd-bugs@xxxxxxxxxx
Subject: Re: misc/39454: UPDATE build of amd64 bootcd fails to pick up new 
kernel
Date: Wed, 3 Sep 2008 21:17:51 +0200

 On Wed, Sep 03, 2008 at 08:52:21PM +0200, Manuel Bouyer wrote:
 > On Wed, Sep 03, 2008 at 08:48:34PM +0200, Havard Eidnes wrote:
 > > >  > 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.
 > > ...
 > > >  '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.
 > > 
 > > Is there a good reason the distrib/amd64/cdrom/ make target needs to
 > > be different from the floppy targets in this respect?
 > 
 > Yes, because it can't be done at the same time (it has to be run after
 > release).
 > 
 > > And why does
 > > not "release" dump the built bits into the appropriate RELEASEDIR
 > > subdirectory?
 > 
 > I think it does, but maybe not when run from the distrib/ dir.
 
 To make is clear; here is what happens:
 
 - 'make distribution' builds from sources, and update binairies in $DESTDIR,
   and builds INSTALL kernels/ramdisks/boot media. This may include bootable
   iso images without binary sets.
 - 'make release' takes whatever is in $DESTDIR and build the release bits
   from it. It won't attempts to rebuild outdated binairies from sources.
 - 'make iso_image' takes whatever is in $RELEASEDIR and makes a
   (possibly bootable) iso image from it.
 
 You have to go though these 3 steps in order to have an updated from sources
 iso image with binary sets.
 
 -- 
 Manuel Bouyer <bouyer@xxxxxxxxxxxxxxx>
      NetBSD: 26 ans d'experience feront toujours la difference
 --
 

<Prev in Thread] Current Thread [Next in Thread>