From owner-freebsd-current Tue Nov 7 0:21:52 2000 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 C74B937B4C5; Tue, 7 Nov 2000 00:21:41 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id eA78LWB31257; Tue, 7 Nov 2000 10:21:33 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id eA78LLZ85437; Tue, 7 Nov 2000 10:21:21 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A07BB80.25A33C9@FreeBSD.org> Date: Tue, 07 Nov 2000 10:21:20 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: current@FreeBSD.org, jdp@FreeBSD.org Subject: Re: Problem with dlopen()/dlsym() after recent crt* changes References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > Why FreeBSD does not link libgcc into shared libraries by default? Everyone > else is doing that. Linking shared libraries with libgcc seems to be the > ultimate work-around. Are there any compatibility problems which are keeping > FreeBSD from doing that? > > > OK, thanks. I'll take a look at it as soon as I can -- hopefully > > tonight. If I can come up with a reasonable work-around, I'll do so. > > > > John > > -- Nope, explicitly linking shared module with -lgcc doesn't solve this problem. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message