On Wed, Sep 29, 2004 at 12:23:47PM -0500, Alex Mauer wrote:> On Wed, 2004-09-29 at 10:29 +0900, Mike Hommey wrote:> libgcypt7-dev is not installed. The program in question statically> links against libexslt.a; the change now requires it to also link> against libgcrypt.a and libgpg-error.a. Is this something that it needs> to check for? It seems to be that it should not be, since libgcrypt and> libgpg-error are not otherwise needed to link against libxslt.

libexslt has now a crypto functionnality which need to use libgcrypt.The static version then has to link all the static libraries needed.If you use libtool for linking, there should not be any problem, it usesthe .la files to get all the dependency chain. If you don't, then, youhave to add libgcrypt and whatever else is needed to your link command.The bug doesn't belong to libxslt1, thus closing the bug.

Mike

I modified the configure script because it couldn't find aclocal-1.4. I have aclocal-1.9.6so I changed the script so that it now finds aclocal (previously it reported "missing")but make still fails with the same error

Quote

creating cache ./config.cachechecking for a BSD compatible install... /usr/bin/ginstall -cchecking whether build environment is sane... yeschecking whether make sets ${MAKE}... yeschecking for working aclocal-1.9... foundchecking for working autoconf... foundchecking for working automake-1.9... foundchecking for working autoheader... foundchecking for working makeinfo... found

Thanks for the suggestion but I want to learn how to fix the problem here rather thaninstall a workaround version. I may not have that option the next time I encounter asituation like this.

I agree with you. Learning the fix is the most satisfying part. The Slackbuilds are good for that too.Just download the slackbuild script and you can see the commands used inside it. They are the same as what you would use in a terminal when you install it to your system.

For example in the link I sent you this is how the build was done in the script.

# Compile the application and install it into the $PKG directorymakemake install It's just another method of doing what you managed to by searching the internet and the archlinux bulletin board. It has one advantage though. When you start getting good at slackbuilds you can then start packaging. That way you would be able to solve the xmlstarlet problem for all vl-users by making it available as a .tlz in the repository.