PATCH: PR other/17783: Top level configure doesn't support shared libraries enabled by default
Geert Bosch
bosch@gnat.com
Thu Nov 4 21:47:00 GMT 2004
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.
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.
-Geert
More information about the Gcc
mailing list