From owner-freebsd-current Wed Jul 22 02:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23616 for freebsd-current-outgoing; Wed, 22 Jul 1998 02:44:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23522 for ; Wed, 22 Jul 1998 02:44:13 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Wed, 22 Jul 1998 10:43:39 +0100 Message-ID: From: Paul Richards To: "'John Birrell'" , dwhite@resnet.uoregon.edu Cc: nrice@emu.sourcee.com, imp@village.org, current@FreeBSD.ORG Subject: RE: Does building current on 2.2.x still work? Date: Wed, 22 Jul 1998 10:43:36 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Would it make sense to install the new mk files during the bootstrap target. The original idea I had for the bootstrap target was to deal with precisely these things, carry out steps required to bootstrap from the previously released version to current. It does mean that you get the mew mk files installed even if the build subsequently fails and you don't install the new version, would this cause any problems since you'd be working with new Makefiles anyway if you'd upgraded your sources to run the bootstrap in the first place. I successfully upgraded from 2.2.5 to current by doing cd /usr/src/share/mk make install and then doing a make world as normal. If there's no other problems just add the above step to bootstrap and make bootstrap the first stage of make world as it was meant to be. Paul Richards Ph.D. Originative Solutions Ltd > -----Original Message----- > From: John Birrell [mailto:jb@cimlogic.com.au] > Sent: Tuesday, July 21, 1998 11:38 PM > To: dwhite@resnet.uoregon.edu > Cc: nrice@emu.sourcee.com; imp@village.org; current@FreeBSD.ORG > Subject: Re: Does building current on 2.2.x still work? > > > Doug White wrote: > > I know that the ___error problem spawns from a libc version > conflict. > > No it doesn't. It results from the world/buildworld not using > -nostdlib > and not finding the libraries it has just built because the library > path is incorrectly set to /usr/obj/usr/src/usr/lib instead of > /usr/obj/usr/src/usr/lib/aout. This is the result of using > old installed > .mk files, hence the need for the -m argument. Changing libc versions > would not have any effect. > > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message