From owner-freebsd-current Sun Feb 11 16: 9:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6663237B491 for ; Sun, 11 Feb 2001 16:09:14 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA12856; Sun, 11 Feb 2001 19:08:45 -0500 (EST) Date: Sun, 11 Feb 2001 19:08:45 -0500 (EST) From: Daniel Eischen To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: installworld gotchas In-Reply-To: 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 Mon, 12 Feb 2001, Bruce Evans wrote: > On Sun, 11 Feb 2001, Daniel Eischen wrote: > > > On Sun, 11 Feb 2001, Daniel Eischen wrote: > > > > > deischen 2001/02/11 14:06:46 PST > > > > > > Modified files: > > > include stdio.h > > > Log: > > > libc MT-safety, part 2. > > > > > > Add a lock to FILE and define an additional flag. > > > > This commit caused some bootstrap problems. The installworld failed > > installing perl which seemed to need sed (from /usr/bin/sed), and libc > > got installed before sed. I used the following to install: > > I think this is telling you that the new libc is incompatible with old > applications. Installworld uses sed from ${INSTALLTMP}/sed. It copies > sed from /usr/bin/sed at the start to (almost) ensure that only the old > version is used. If perl actually uses /usr/bin/sed, then that is > another bug in perl, but since perl is installed before sed, this makes > no difference because /usr/bin/sed is still the old version. The new libc is incompatible with some old applications, but I'm not too sure why. The lock was added at the end of FILE... -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message