[xmlsec] xmlsec: compilation on IBM AIX 4.3 , core dump

Aleksey Sanin aleksey@aleksey.com
Thu, 29 May 2003 17:25:28 -0700


<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=KOI8-R">
  <title></title>
</head>
<body>
<br>
<br>
<blockquote type="cite" cite="mid200305292356.QAA15819@scn4.scn.org">
  <pre wrap="">The AIX compiler doesn't like the -Wall option in
src/openssl/Makefile</pre>
</blockquote>
Ops, it's a bug. Thanks for reporting it! The fix is commited to CVS.<br>
<br>
<blockquote type="cite" cite="mid200305292356.QAA15819@scn4.scn.org">
  <pre wrap="">but I get some warnings </pre>
</blockquote>
What kind of warnings do you have?<br>
<br>
<br>
<br>
<blockquote type="cite" cite="mid200305292356.QAA15819@scn4.scn.org">
  <pre wrap="">and all the tests done during "make check"
core dump.
  </pre>
</blockquote>
Hm.. It should not core dump on this line! The only reason I can
imagine is <br>
if you mix OpenSSL libraries: compile with one headers/libraries and
trying<br>
to load another one. Try to compile xmlsec with static linking
(--enable-static-linking<br>
option for ./configure script) thought I don't know will it work on AIX
or not.<br>
<br>
<br>
<blockquote type="cite" cite="mid200305292356.QAA15819@scn4.scn.org">
  <pre wrap="">% dbx /usr/local/bin/xmlsec1 core
Type 'help' for help.
reading symbolic information ...
[using memory image in core]

Segmentation fault in glink.xmlSecErrorsGetMsg at
0xd2736b80 ($t1)
0xd2736b80 (xmlSecErrorsGetMsg+0x8) 800c0000        lwz  
r0,0x0(r12)
(dbx) where
glink.xmlSecErrorsGetMsg() at 0xd2736b80
xmlSecOpenSSLErrorsInit(), line 202 in "crypto.c"
xmlSecOpenSSLInit(), line 38 in "crypto.c"
xmlSecAppCryptoInit(0x0), line 33 in "crypto.c"
xmlSecAppInit(), line 1857 in "xmlsec.c"</pre>
</blockquote>
<br>
It just could not crash there!!! The only case is if you have problems
with linking/loading<br>
libraries dynamicaly (compile with one and load another version). Try
the static linking<br>
and check your LD_LIBRARY_PATH variable.<br>
<br>
<br>
Aleksey.<br>
<br>
P.S. Please subscribe to xmlsec mailing list. It's very difficult to
dig up your messages<br>
from tons of "xmlsec feel younger", "xmlsec, by viagra today!" and so
on.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>