From owner-freebsd-questions@FreeBSD.ORG Thu Nov 1 18:07:05 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57C1716A41A for ; Thu, 1 Nov 2007 18:07:05 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 01C2213C48D for ; Thu, 1 Nov 2007 18:07:04 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from [192.168.2.62] (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (AUTH: LOGIN seklecki, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by wingspan with esmtp; Thu, 01 Nov 2007 12:04:26 -0400 id 00056452.4729F90A.000184CA From: "Brian A. Seklecki" To: Giorgos Keramidas In-Reply-To: <20071031174533.GA33931@kobe.laptop> References: <20071030180139.Y81307@arbitor.digitalfreaks.org> <20071031115412.GD3140@kobe.laptop> <1193843040.4419.9.camel@ingress.pitbpa0.priv.collaborativefusion.com> <20071031164101.GC33211@kobe.laptop> <20071031132514.E81307@arbitor.digitalfreaks.org> <20071031174533.GA33931@kobe.laptop> Date: Thu, 01 Nov 2007 12:04:25 -0400 Message-Id: <1193933065.3974.38.camel@ingress.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.10.3 (2.10.3-4.fc7) Cc: freebsd-questions@FreeBSD.ORG Subject: iso.1 target and release(8) in RELENG_7 (WAS: Re: release(8) environmental variables) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 18:07:05 -0000 Here's some fun -- I'm pretty sure this worked in RELENG_6: "make release" in /usr/src/release into RELEASEDIR=/opt/releasedir The rebuild completes (release.1 -> release.8), the kernels are built, the file system layout is prepared (ftp.1 -> cdrom.3), then (I think) the iso.1 target is called and the images are zero-bytes. Log excerpts below... Either I'm confused, I have my environmental variables set wrong, or this is broken. :) 1) My $LOCAL_SCRIPT properly copies mkisofs(1) and mkhybrid(1) into place in the $CHROOTDIR/usr/bin $ ls -al /opt/relchroot/usr/bin/mkisofs -r-xr-xr-x 1 root wheel 510712 Nov 1 02:13 /opt/relchroot/usr/bin/mkisofs 2) On the root of the system, I have to make /R a sylink to /opt/relchroot/R to make "make iso.1" succeed : # ls -al /R lrwxr-xr-x 1 root wheel 16 Oct 29 23:20 /R -> /opt/relchroot/R Other-wise: [root@build-fbsd-releng7-amd64 /usr/src/release]# make iso.1 Creating ISO images... mkisofs: No such file or directory. Invalid node - /R/cdrom/bootonly *** Error code 2 Stop in /usr/src/release. 3) I don't see how $CHROOTDIR is used in /usr/src/release/Makefile at: iso.1: [...] Unless, when not run as a manual target outside of the chroot(), it runs in the chroot and /R is relative to $CHROOTDIR?. That would make sense of the error in the log excerpt below matched what I encounter on the command line as a manual run. I'm setting: # applies to build export DESTDIR=/opt/dest export MAKEOBJDIRPREFIX=/opt/obj export RELEASEDIR=/opt/release export CHROOTDIR=/opt/relchroot This is a shell script that runs nightly -- it worked in RELENG_6. ~BAS [...] Created /R/stage/floppies/boot.flp touch floppies.1 touch floppies.3 Setting up FTP distribution area 0 blocks 0 blocks touch ftp.1 Building CDROM live filesystem image 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks 0 blocks Copy GENERIC kernel to boot area Setting up CDROM boot area touch cdrom.1 Building CDROM disc1 filesystem image 0 blocks 0 blocks Building CDROM disc2 filesystem image touch cdrom.2 Building bootonly CDROM filesystem image touch cdrom.3 Release done [...] On Wed, 2007-10-31 at 19:45 +0200, Giorgos Keramidas wrote: > On 2007-10-31 13:26, "Brian A. Seklecki" wrote: > >>> really sucks. > >> > >> I believe that's intentional, so re-running "make release" with > >> different CHROOTDIR values will produce consistently "similar" binaries. > > > > I use LOCAL_SCRIPT to copy /etc/make.conf (well, /etc/src.conf) into place > > inside the jail for the rebuild so that I can build a custom internal > > release w/o certain subsystems (IPv6 or CSH, for example) > > > > Is there a better way to do it? > > LOCAL_SCRIPT sounds fine to me :) > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > > > >