Re: Linking errors with libxslt2 on Solaris 9 (now with "install -D" fixes!) khyron4eva
From: khyron4eva@xxxxxxxxx
To: users@xxxxxxxxxxxxxxxx
Subject: Re: Linking errors with libxslt2 on Solaris 9 (now with "install -D" fixes!)
Date: Mon, 16 Oct 2006 10:51:52 +0200 (CEST)
I solved the problem by re-arranging the order of the library directories in
my LD_LIBRARY_PATH. As long as the directory containing libxslt.so appears
first, the build appears to work.
I noticed a thread about "install -D" as well, and I have run into this
problem. During the install-library phase, libtool attempts to run "install
-D" but I'm guessing that "configure" never explicitly searches for an
"install" binary that accepts the "-D" flag. GNU install appears to. It is a
part of the GNU coreutils, which I downloaded from www.sunfreeware.com. So
once I figure out how to hack that to work correctly, everything should be
golden. But the configure script really needs to:
1. Make sure a GNU compatible install is in the path in the correct location,
and fail if not.
2. "man -s 1b install" on Solaris 9 shows that the BSD install does not use
"-D", so checking for a BSD compatible install is insufficient.
3. libtool should use ginstall in its install mode.
4. By changing the following, I was able to hack this install target to work:
A. Edit all lines reading as
$(LIBTOOL) --mode=install install
to read as
$(LIBTOOL) --mode=install ginstall
in the generated lib/Makefile and utils/Makefile
B. For the target "install-modxslt-config:" in utils/Makefile, changing
"install" to "ginstall"
C. Using "gmake INSTALL=/usr/local/bin/ginstall install" to perform the
install.
5. The "install-modxslt-config:" target was REALLY insidious. That should be
using $(INSTALL) instead of the hardcoded "install" command.
Also note that in my instance, I symlinked /usr/local/bin/ginstall to
/usr/local/bin/install since it is a not a natural pathname. Same thing for
gmake - it is a symlink to /usr/local/bin/make. Both are installed from
packages prepared at www.sunfreeware.com.
6. I find this configuration assumes a lot of Linux-y things. If there'e some
way I can encourage better Solaris support, please let me know.
