This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: can't resolve symbol '__register_frame_info'


On Wed, 3 June 1998, 09:55:05, korbb@datadesign.com wrote:

 > Whatever that is.
 > 
 > Egcs compiles itself and the  result runs, but my program
 > fails to load with this error...
 > 
 > Que pasa?
 > 
 > 

I just faced this myself on my newly installed RedHat  5.0 ;-) (Yes, I
finally got it running after  two unsuccessfull installations - broken
PS/2 SIMMs :-( )

Yesterday I built KDE4 using egcs-1.0.3a; this includes e.g. libjpeg.so.
Everything got installed in /tools/session/sde4/{include,lib}.

I  then tried to  build   ImageMagick-4.0.6; its configure used   this
directory for linking: "-L/tools/session/sde4/lib"; but, it didn't add
a "-Wl,-rpath,/tools/session/sde4/lib"  to  make sure  _this_  library
will be  used by the runtime linker  /lib/ld-linux.so.2; hence it used
the libjpeg.so from /usr/lib, which is the official RedHat one and had
been built by a gcc-2.7.2.x compiler.

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.

Manfred.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]