From owner-freebsd-current Tue Jan 9 16:14:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 801A637B400; Tue, 9 Jan 2001 16:13:53 -0800 (PST) Received: from vic.sabbo.net (vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f0A0Dkv08951; Wed, 10 Jan 2001 02:13:48 +0200 Received: (from max@localhost) by vic.sabbo.net (8.11.1/8.9.3) id f0A0Dla02999; Wed, 10 Jan 2001 02:13:47 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200101100013.f0A0Dla02999@vic.sabbo.net> Subject: Re: Problems related to disappearnce of libgcc_r To: peter@netplex.com.au (Peter Wemm) Date: Wed, 10 Jan 2001 02:13:42 +0200 (EET) Cc: current@FreeBSD.ORG, sobomax@FreeBSD.ORG (Maxim Sobolev) In-Reply-To: <200101092204.f09M45G25580@mobile.wemm.org> from "Peter Wemm" at Jan 09, 2001 02:04:05 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "David O'Brien" wrote: > > On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: > > > I wonder if anyone noticed that disappearance of libgcc_r will cause lot of > > > ports to break. Therefore it would be nice if some form of compatibility sh > im > > > is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ > r.a > > > automatically created by installworld would do the trick nicely. > > > > I really don't want to propogate libgcc_r. Lets just fix the ports that > > break. They can be seen at http://bento.freebsd.org/ > > We need to be a little careful for ports that are supposed to work on > RELENG_4 and -CURRENT. Yes, it's why I think we need this compatability hack. Bloating all 20+ ports that have to use gcc_r on 4-STABLE and downwards with OSVERSION check is PITA. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message