From owner-freebsd-questions Sat Sep 28 0:26: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A56737B401 for ; Sat, 28 Sep 2002 00:26:06 -0700 (PDT) Received: from longfellow.nbrewer.com (nbrewer.dsl.visi.com [208.42.141.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF24443E6E for ; Sat, 28 Sep 2002 00:26:05 -0700 (PDT) (envelope-from chris@northernbrewer.com) Received: by longfellow.nbrewer.com (Postfix, from userid 1001) id D07BB1886; Sat, 28 Sep 2002 02:26:04 -0500 (CDT) Date: Sat, 28 Sep 2002 02:26:04 -0500 From: Christopher Farley To: freebsd-questions@freebsd.org Subject: Help! Broken libc! Message-ID: <20020928072600.GA321@northernbrewer.com> Mail-Followup-To: Christopher Farley , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Organization: Northern Brewer, St. Paul, MN Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I believe that one of my machines has a hardware problem that occasionally corrupts disk writes. As luck would have it, I also suspect that my /usr/lib/libc.so.4 became corrupt during my last buildworld a few days ago. I now get 'internal compiler errors' whenever I try to compile any program with g++. I compared the md5 hashes of various system files to those of another 4.7-RC machine I updated at about the same time. The libc.so.4 hash is different, so I suspect it may be the source of my problem. It also appears that replacing this file is somewhat non-trivial. When I attempt to remove the file, I get an "Operation not permitted," probably because it's linked to a ton of running programs. Is there even a way to replace this file? -- Christopher Farley www.northernbrewer.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message