Hi Zach, Tim, 

Zach <[EMAIL PROTECTED]> writes:

> Similar to the approach in another thread, I replaced all occurrences of
> ${XLIB}/libXpm.a with -lXpm in the Makefile.pamphlet file.  I believe that
> such a replacement will make this work on my system (and others like it) but
> not break any other installations.  The linker should automatically look for
> libXpm.a and libXpm.so on the linker directories when it encounters a -l
> flag, right?  Why is the libXpm archive's path hard coded into makefile
> maker?

Zach, thanks for your report!

Without a configure stage in the build process, we are basically stuck with
hard-wired paths.  That said, the attached patch should work for generic linux
distros.  It appeals to the search paths which the linker follows by default in
addition to /usr/X11R6/lib.

I built a fresh checkout with this patch against slackware 11, which does have
libXpm.a, and all is well (so no backwards breakage, AFAICT).

Tim, could you consider this patch in your next build/test cycle?

Thanks,
Steve

diff --git a/Makefile.pamphlet b/Makefile.pamphlet
index 0c6eb1d..9f6b15a 100644
--- a/Makefile.pamphlet
+++ b/Makefile.pamphlet
@@ -1236,7 +1236,7 @@ PLF=LINUXplatform
 # C compiler flags
 CCF="-O2 -fno-strength-reduce -Wall -D_GNU_SOURCE -D${PLF} -I/usr/X11/include"
 # Loader flags
-LDF=" -L/usr/X11R6/lib ${XLIB}/libXpm.a "
+LDF=" -L${XLIB} -lXpm "
 # C compiler to use
 CC=gcc 
 AWK=gawk
_______________________________________________
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer

Reply via email to