I was able to compile on HP-UX 9.xx by grabbing the xpm libs, compiling
them in a local directory for use, and then giving the path as part of the
LOCAL_LDFLAGS environmental pointer for the linker. My "gccopts"
single-line script (I don't use this often enough to remember it without
such help) is:
setenv LOCAL_LDFLAGS "-I/usr/user2/tiefen/lib -L/usr/lib/X11R5
-L/usr/user4/tiefen/Xpm/lib -L/usr/user2/tiefen/lib"
(The mailer has split the command onto 2 lines, please note.) Any other
and better suggestions from others I will probably incorporate in place of
this. By the way, dynamically linked things such as this remember where
the lib is. I don't know enough about how these things are found by the
loader to understand this, but when I compiled fvwm2 on another system
with a different xpm path and copied the binaries over to the target
system, the loader couldn't find the xpm lib in my directory hierarchy. I
had to do a compile and link locally before it could get it correctly.
However, I couldn't find an explicit path to the xpm lib in either
executable with "strings". To me, it is a mystery....
Michael Tiefenback
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Sep 12 1997 - 07:39:51 BST