Prelude:
I vaguely remember (but cannot Google the details) a scene in one of
the Discworld novels (RIP Sir Terry) where in the middle of a spell
a wizard has so invoke something like "the guardian spirits of white
mice no more than three inches long" and then makes a smug comment,
roughly "You have *no* idea how much research *that* took!".
That is how I feel right now.
I was having problems because I unpacked the GnuPG source archive in a
directory that I had accessed through a path that contained sybolic
links. I have been doing this for all software packages for many
years and it has never been a problem until now.
The GnuPG tests try to ensure that everything is sane by checking that
$GNUPGHOME is the current directory. When that equality is tested,
the path on one side has had its symbolic links resolved whereas the
path on the other side has not. So the test incorrectly fails if the
top directory path contains symbolic links.
Details:
Automake recognises a special variable TESTS_ENVIRONMENT . If you set
"TESTS_ENVIRONMENT = foo=bar" in Makefile.am then Makefile.in will
ensure that all tests run with foo=bar in the environment. The GnuPG
build system uses this hook to set $GNUPGHOME . But there is an
inconsistency...
In tests/ and tests/pkits/ we have:
GNUPGHOME=`/bin/pwd`
whereas in tests/openpgp/ we have:
GNUPGHOME=$(abs_builddir)
I attach a sed script that fixes this inconsistency. If you run it
before configuring then the tests pass even when the top directory
path contains symbolic links.
Regards,
Jeremy Henty
#!/bin/sh
sed -i \
-e 's|\(GNUPGHOME\)=\$(abs_builddir)|\1=`/bin/pwd`|' \
tests/openpgp/Makefile.in
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
