%% Andrew Laden <andrew_at_sgc.com> writes:
al> Compiled with no problem or errors. When I tried to run it i got.
al> # ./conftest
al> ld.so.1: ./conftest: fatal: libXpm.so.4.11: can't open file: errno=2
al> Killed
This means that, while the linker can find the shared lib just fine
because you specified -L, the runtime can't find it. Note that there is
a distinction between linktime paths and runtime paths--older systems
like SunOS didn't make this distinction (or not easily), but newer ones
do.
This means that you don't have your ld.so environment set up correctly.
On Solaris, for example, you can specify the runtime path by either
setting the LD_RUN_PATH env. variable or the -R option at link time. If
your xpm libraries are in a non-standard place, you _must_ provide one
or the other of these methods for finding it a runtime (or set
LD_LIBRARY_PATH at runtime).
Unfortunately, at this time GNU autoconf (and thus fvwm) doesn't handle
this situation very well :(. We hope to improve this in the future (see
the BUGS file). Until then, you'll have to do something like:
$ LDFLAGS=-R/opt/fvwm/lib ./configure --prefix=/opt/fvwm ...
to explicitly set the -R option.
What really confuses me is why you didn't see this output (or any other
output) in the config.log file. It should have been there...
Oh well.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Jan 29 1999 - 15:36:59 GMT