From owner-freebsd-current Sat Jun 21 23:50:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA13218 for current-outgoing; Sat, 21 Jun 1997 23:50:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13150 for ; Sat, 21 Jun 1997 23:49:53 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA23309; Sun, 22 Jun 1997 16:38:58 +1000 Date: Sun, 22 Jun 1997 16:38:58 +1000 From: Bruce Evans Message-Id: <199706220638.QAA23309@godzilla.zeta.org.au> To: jdp@polstra.com, jkh@time.cdrom.com Subject: Re: Hmmmm, this is new.. Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> They should not be happening. It looks a lot like your system has >> lost its /usr/lib/libm.so.3.0. The Makefile for libtcl adds "-lm" > >Hmmm. There may be something in the release building process which >actually causes this - let me investigate further, and sorry for >the false alarm if it turns out to be one. It's probably a bug for it not to happen for every `make world'. -nostdlib should be used to prevent old libraries being linked to. Since libtcl is built before msun and there is no special bootstrapping for msun, a new version of msun is guaranteed to not exist when libtcl is linked. The release attempts to avoid problems like this by building in a chrooted tree. Apparently it is not careful enough. I think linking to a 2.2 libm.so would work but linking to a 2.1 libm.so would fail. Bruce