Subject: Re: split out libraries from gcc3-c?
To: John R. Shannon <email@example.com>
From: Jeremy C. Reed <firstname.lastname@example.org>
Date: 12/19/2003 10:48:43
On Fri, 19 Dec 2003, John R. Shannon wrote:
> libgcc contains calls to a macro declared procedure:
> __enable_execute_stack (void *)
> that results in an error like the following when you link libgcc into a shared
> library on many platforms:
> /usr/bin/ld: gate-in.exe: hidden symbol `__enable_execute_stack' in
> /lib/gcc-lib/i386--netbsdelf2.0/3.3.2/libgcc.a(_trampoline.oS) is referenced
> by DSO
> The call is in macro TRANSFER_FROM_TRAMPOLINE. It's called in
> Have you encountered this yet?
No I have not seen that. (I am curious: does this have anything to do with
libgcc versus libgcc_s ?)
The libraries installed with my gcc3-c++-lib package (as far as I know) is
no different that the gcc3-c++ (currently) libraries.
> On Friday 19 December 2003 11:18 am, Jeremy C. Reed wrote:
> > I made a gcc3-c++-lib package. (Maybe it should have different name.)
> > It installs the libraries and headers (like gcc3/lib/libstdc++.so.5 and
> > gcc3/include/c++/3.3.2/istream).
Has anyone worked on making a gcc3-c-lib package (so
gcc3/lib/libgcc_s.so.1 and related are available without compiler)?
Jeremy C. Reed