From owner-freebsd-current Fri Mar 10 10:10:37 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA20428 for current-outgoing; Fri, 10 Mar 1995 10:10:37 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA20421 for ; Fri, 10 Mar 1995 10:10:33 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id KAA02164; Fri, 10 Mar 1995 10:10:12 -0800 From: "Rodney W. Grimes" Message-Id: <199503101810.KAA02164@gndrsh.aac.dev.com> Subject: Re: HEADS UP - About removing libgcc.so.261 To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Fri, 10 Mar 1995 10:10:11 -0800 (PST) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199503101758.JAA04141@ref.tfs.com> from "Poul-Henning Kamp" at Mar 10, 95 09:58:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 887 Sender: current-owner@FreeBSD.org Precedence: bulk > > > HEADS UP, YOUR X11 MIGHT STOP WORKING ON YOU!!!! > > > > A few days ago the building of libgcc.so.261.0 was removed from the > > gcc build, and for good reason. But.... > > > > I just ran into a major problem with removing the shared version of > > gcc (libgcc.so.261.0), it seems that XFree86 3.1 is dynamically linked > > against this. > you shouldn't remove it until you are sure you don't need it... It was not a matter of removing it that caused me a problem, I built a release and installed a new machine, then I installed X. Natuarally X would not come up due to the missing lib. This is a problem for you to think about both in the next snap shot [ie, a warning in the install notes], and in the next release. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD