From owner-freebsd-current Tue Jul 21 13:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01471 for freebsd-current-outgoing; Tue, 21 Jul 1998 13:18:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01412 for ; Tue, 21 Jul 1998 13:17:57 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.5/8.8.8) with SMTP id NAA17873; Tue, 21 Jul 1998 13:17:27 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Jul 1998 13:17:27 -0700 (PDT) From: Doug White To: Norman C Rice cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Does building current on 2.2.x still work? In-Reply-To: <19980721155716.A20739@emu.sourcee.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Jul 1998, Norman C Rice wrote: > On Tue, Jul 21, 1998 at 12:58:13PM -0600, Warner Losh wrote: > > In message <19980721130054.A20330@emu.sourcee.com> Norman C Rice writes: > > : > of things: if ld doesn't die missing ___error (when BINFORMAT=aout), it's > > > > cd /usr/src > > sudo make -m /usr/src/share/mk world > > > > Is all you need to do to upgrate from -stable to -current. Substitute > > buildworld if you just want to build. > > > > Note that using the relative path won't work, nor will trying to > > define things on the command line. > > Perhaps my intent was unclear. I was trying to let Doug know that > using the relative path can/will `break' the build and spew the infamous > ``___error'' messages. I thought as keeper of the FAQ this might be of > interest to Doug. AFAIK, use of the relative path also breaks updates > of -current. I know that the ___error problem spawns from a libc version conflict. The last time I had current on this box they switched the libraries over, and the next day's build exploded. I remembered the discussion from -hackers about it, copied /usr/lib to /usr/lib/aout, re-ldconfig'd, and the build went smoothly. Also, the above published solution has not exploded yet .. It's chewing on liF77 now. (building from work over dialup just doesn't do great things for speding up the build.) I just remembered I have MACHINE_ARCH and BINFORMAT defined in make.conf; hope that doesn't confuse anything. > make -m /usr/src/share/mk buildworld > make -m /usr/src/share/mk installworld I'm not too much in favor of sticking -current-isms in the FAQ, but we could make an exception. Or Nik could drop it onto the tutorial (which was one of the places I checked, along with /usr/src/Makefile and the commit logs for said Makefile and make.conf). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message