From owner-freebsd-current  Sun Jun  9 07:14:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA02100
          for current-outgoing; Sun, 9 Jun 1996 07:14:31 -0700 (PDT)
Received: from luke.pmr.com (luke.pmr.com [206.224.65.132])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02073
          for <freebsd-current@freefall.FreeBSD.org>; Sun, 9 Jun 1996 07:14:24 -0700 (PDT)
Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.6.9) id JAA29772 for freebsd-current@freefall.cdrom.com; Sun, 9 Jun 1996 09:14:31 -0500 (CDT)
From: Bob Willcox <bob@luke.pmr.com>
Message-Id: <199606091414.JAA29772@luke.pmr.com>
Subject: Libc compatibility in -current??
To: freebsd-current@freefall.FreeBSD.org (freebsd-current)
Date: Sun, 9 Jun 1996 09:14:31 -0500 (CDT)
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Lately I have been having what appears to be compatibility problems
with libc.so.3.0 when I do a make world on my systems running
-current.  Starting on June 3rd (my most recent make world prior
to that was May 31st) any attempt to run make world crashes in a
horrible way right after it has installed a newly built version of
libc.so.3.0 in /usr/lib.  After that no comand that uses libc.so.3.0
will work (i.e., I get core dumps at a frantic rate).  To restore
the system to an operational state I must boot up in single user
mode and replace this library with the previous version.

I have re-supped and retried this several days in a row (even tried
it on a different system) with the same result.  Is anybody else
seeing this problem?  Am I missing something that happened between
May 31 and June 3 that I should have done and didn't?  I am getting
to my wits end here and don't know what to try next.

Thanks,
-- 
Bob Willcox
bob@luke.pmr.com
Austin, TX