This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: can't resolve symbol '__register_frame_info'
- To: manfred at s-direktnet dot de, Manfred dot Hollstein at ks dot sel dot alcatel dot de
- Subject: Re: can't resolve symbol '__register_frame_info'
- From: Bruce Korb <korbb at datadesign dot com>
- Date: Thu, 04 Jun 1998 13:03:59 -0700
- CC: egcs at cygnus dot com
- Organization: Data Design Systems
- References: <35757FE9.87EEC06D@datadesign.com> <13686.53201.340176.596631@saturn.hollstein.net>
- Reply-To: ddsinc09 at ix dot netcom dot com
Manfred Hollstein wrote:
> To fix the problem, you should
>
> 1. Add all directories which contain _your_ private shared libs
> to LD_RUN_PATH prior to linking your executables, and/or
> 2. Add a -Wl,-rpath,<dir> for all these directories, or
> 3. Remove all your own lib*.so files from your private directories.
>
> Since I didn't want to use KDE4's libjpeg.so, I removed libjpeg.so
> (and libgdbm.so) from my private installation directory and re-linked
> the particular applications; now ImageMagick is running like a charm.
Excuse me? What happened to LD_LIBRARY_PATH?
Are there *two* ways of specifying the same information?
Also, for the particular application, I am using :
ltmain.sh (GNU libtool) 1.2
which builds a shared lib for me and a magical shell script that
is supposed to do the right thing when invoking the uninstalled
program. So, does libtool need updating to work with egcs?