[gs-bugs] [Bug 690671] missing libstdc++ not detected by autogen.sh

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon May 17 10:39:08 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=690671

--- Comment #6 from Chris Liddell <chris.liddell at artifex.com> 2010-05-17 10:39:07 UTC ---
This is system configuration problem with the default Solaris installation. It
is setup to allow gcc (with the Sun linker) to link executables against the
shared libstdc++ (and other libs in there) in /usr/sfw/lib but the dynamic
linker search path does not include that path. It is not a problem with autconf
or our use of autoconf - the configure script correctly decides that the linker
can create an executable linked to libstdc++.so - autoconf is not intended to
check the configuration of the run-time linker.

I would think that the correct course of action is to report this to the
freeware Solaris tools maintainers at Sun.

There are two solutions. If you have superuser privileges on the system, you
can permanently update the run-time/dynamic linker search path with:

crle -u -l /usr/sfw/lib

The "-u" is /vital/ is it updates/appends to, rather than overwrites the
default library search path.

If you can't get superuser rights, setting:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/sfw/lib

This needs to be set for every shell you spawn (so best done in .profile, or
whatever) because the gs executable itself is also linked against libstdc++.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list