On Tue, Aug 06, 2019 at 05:07:20AM +0100, Ken Moffat via blfs-dev wrote:
> On Sun, Aug 04, 2019 at 10:49:48PM -0500, Douglas R. Reno wrote:
> > On 2019-08-04 21:40, Ken Moffat via blfs-dev wrote:
> > > On Sun, Aug 04, 2019 at 11:55:21PM +0100, Ken Moffat via blfs-dev wrote:
> > >
> > > With added xmlsec-1.2.28 and --with-system-xmlsec it built and
> > > installed.
> > >
> > > I've no idea how you guys manage to build it with current versions
> > > of everything, but (in the words of Dragons' Den from TV or youtube)
> > > I'm close to "I'm out."
> > >
With libreoffice-6.3, xmlsec-1.2.28 is in the list of what gets
downloaded, so this problem will presumably disappear.
Arguably, xmlsec1 should still be in the book (like raptor, rasqal,
etc). But I don't understand the testsuite, it skips almost
every test. Ah, from the log it created in /tmp:
Error: parameter "--X509-skip-strict-checks" is not supported or the requested
feature might have been disabled during compilation.
Error: invalid parameters
Unknown command
Usage: xmlsec <command> [<options>] [<files>]
xmlsec is a command line tool for signing, verifying, encrypting and
decrypting XML documents. The allowed <command> values are:
--help display this help information and exit
--help-all display help information for all commands/options and exit
--help-<cmd> display help information for command <cmd> and exit
--version print version information and exit
--keys keys XML file manipulation
--sign sign data and output XML document
--verify verify signed document
--sign-tmpl create and sign dynamicaly generated signature template
--encrypt encrypt data and output XML document
--decrypt decrypt data from XML document
(etc)
The configure script talks about X509 options, but it reports the
result of checking (against openssl) as 'x509' which made finding
what it did/didn't run a bit harder. I think this is a
bug in the testsuite.
If I use
sed -i 's/--X509-skip-strict-checks//' tests/testrun.sh
a lot more tests get run, with occasional skips, but all the AES-GCM
tests still skip, with messages in the log like
/tmp/xmlsec1-1.2.28/apps/xmlsec1 check-transforms --crypto nss
--crypto-config /tmp/xmlsec-crypto-config aes128-gcm
Error: transform "aes128-gcm" not found
I imagine that our build of openssl does not support AES-GCM.
ĸen
--
Adopted by dwarfs, brought up by dwarfs. To dwarfs I'm a dwarf, sir.
I can do the rite of k'zakra, I know the secrets of h'ragna, I can
ha'lk my g'rakha correctly ... I am a dwarf
Captain Carrot Ironfoundersson (in The Fifth Elephant)
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
