I tried to perform some examples in xmlsec1-1.2.16.tar.gz on a
Linux x86_64 box.

[user@x86_64 examples]$ make sign1 verify1
  (snip)
[user@x86_64 examples]$ ./sign1 sign1-tmpl.xml rsakey.pem > foo.xml
func=xmlSecDSigCtxProcessSignatureNode:file=xmldsig.c:line=463:obj=unknown:subj=dsigCtx->signValueNode == NULL:error=100:assertion: 
func=xmlSecDSigCtxSign:file=xmldsig.c:line=303:obj=unknown:subj=xmlSecDSigCtxSigantureProcessNode:error=1:xmlsec library function failed: 
Error: signature failed

My try failed as above.  Then I tried to perform same example on
a Linux i686 box.

[user@i686 examples]$ make sign1 verify1
  (snip)
[user@i686 examples]$ ./sign1 sign1-tmpl.xml rsakey.pem > foo.xml
[user@i686 examples]$ ./verify1 foo.xml rsapub.pem 
Signature is OK


I found a following article.

http://www.aleksey.com/pipermail/xmlsec/2007/008005.html

I think that following part in xmlsec1.spec causes this problem.

# positively ugly but only sane way to get around #192756
sed 's+/lib64+/$archlib+g' < xmlsec1-config | sed 's+/lib+/$archlib+g' | sed 's+ -DXMLSEC_NO_SIZE_T++' > xmlsec1-config.$$ && mv xmlsec1-config.$$ xmlsec1-config


I removed third sed command and tested same example on x86_64 and
i686 box.  And then, both test succeeded.

[user@x86_64 examples]$ ./sign1 sign1-tmpl.xml rsakey.pem > foo.xml 
[user@x86_64 examples]$ ./verify1 foo.xml rsapub.pem 
Signature is OK


I hope this fix does not break another part of the package.