This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: PR other/17783: Top level configure doesn't support shared libraries enabled by default
On Thu, Nov 04, 2004 at 04:47:13PM -0500, Geert Bosch wrote:
> On Nov 4, 2004, at 12:09, H. J. Lu wrote:
> >I checked it into gcc 4.0, 3.4 and src.
> I just note that it still is the case that when an executable is
> moved, it will not be able to find libunwind. This is a
> regression from earlier versions of GCC and I wonder if there
> is a way to retain this behavior.
I don't think it has changed. Did your executable use libgcc_s.so.1
before? When you moved the executable, which libgcc_s.so.1 was used?
I don't think the newly built libgcc_s.so.1 was used. The only
difference here is libgcc_s.so.1 vs. libunwind.so.7. See
> Is it possible to specify that libunwind be linked in statically?
> It would be nice to add a note to the release about this changed
> behavior and possible workarounds.