[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] Build problem on Slackware Linux 12
From: |
Zach |
Subject: |
[Axiom-developer] Build problem on Slackware Linux 12 |
Date: |
Wed, 30 Apr 2008 11:53:02 -0600 |
This is similar to other (old) problems I saw on the list archives.
This is regarding axiom pulled from git on April 29th 2008 (which I
guess is a Silver source, my bad, I was looking for a Gold, but
whatever). Basically something from graph wants to link against
libXpm.a. However, my installatio (and I haven't touched it for the
most part), not only doesn't contain libXpm.a in /usr/X11R6/lib, it
doesn't have this library at all AFAIK. It only has a libtoolized
archive, i.e. libXpm.la, and the shared libraries
libXpm.so.<version>. I don't know much about libtool, but from
what I can tell this is a script wrapper that hides the actually
archive. Anyway, I should be able to use the shared library files,
right? Here is some info:
address@hidden:~$ uname -a
Linux marco 2.6.23.9MYTH-TV #4 SMP Mon Dec 17 05:46:46 MST 2007 i686 AMD Duron(tm) Processor AuthenticAMD GNU/Linux
address@hidden:~$ locate libXpm.a
address@hidden:~$ locate libXpm
/var/log/packages/libXpm-3.5.6-i486-1
/var/log/scripts/libXpm-3.5.6-i486-1
/usr/lib/libXpm.so.4.11.0
/usr/lib/libXpm.so.4
/usr/lib/libXpm.la
/usr/lib/libXpm.so
address@hidden:~$ file /usr/lib/libXp
libXp.la libXpm.so.4 libXprintUtil.la
libXp.so libXpm.so.4.11.0 libXprintUtil.so
libXp.so.6 libXprintAppUtil.la libXprintUtil.so.1
libXp.so.6.2.0 libXprintAppUtil.so libXprintUtil.so.1.0.0
libXpm.la libXprintAppUtil.so.1
libXpm.so libXprintAppUtil.so.1.0.0
address@hidden:~$ file /usr/lib/libXpm.la
/usr/lib/libXpm.la: libtool library file
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?
I am still working on the build (old computer), but it appears to
be on the testing stage without problems, so it seems to have worked.
Zach
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Axiom-developer] Build problem on Slackware Linux 12,
Zach <=