SASL on AIX 5.x
Chapman, Kyle
Kyle_Chapman at G1.com
Thu Oct 20 11:58:25 EDT 2005
what i have done on aix:
1. build libtool-1.x.x
2. run configure <options>
3. mv old libtool (libtool.old) cp the newer libtool into the cyrus dir
4. make
5. cd into plugins/.libs and you should see shared objects (use ldd to verify if you like)
it does create .so files, but then the newer libtool does what aix expects with them which is drop them into the .a. libsasl2.a (which has a shared lib as an archive member) will look for /usr/lib/sasl2/lib<mech>.so (no suprise). after install, the dir will only have .a's which you will need to extract the .so's from
for sure other folks will have probably far better means to do all this...
-----Original Message-----
From: Tim Alsop [mailto:Tim.Alsop at CyberSafe.Ltd.UK]
Sent: Thursday, October 20, 2005 11:44 AM
To: Chapman, Kyle; cyrus-sasl at lists.andrew.cmu.edu; jorma.heikkuri at pp.inet.fi; walter+sasl at efrei.fr
Subject: RE: SASL on AIX 5.x
Kyle,
I am not sure how I can use the SASL configure so it uses the new libtool, because the config sub directory contains the 1.3.5 version of libtool, which is used when I run the SASL configure command. Do you know if it is possible to setup the SASL build environment to use the new version instead of old ? If I copy a new libtool into the SASL directory, then this will be overwritten with the 1.3.5 version each time I build ...
Thanks again,
Tim
_____
From: Chapman, Kyle [mailto:Kyle_Chapman at G1.com]
Sent: 20 October 2005 16:40
To: Tim Alsop; cyrus-sasl at lists.andrew.cmu.edu; jorma.heikkuri at pp.inet.fi; walter+sasl at efrei.fr
Subject: RE: SASL on AIX 5.x
ftp.gnu.org/gnu/libtool or another mirror
it was 1.4.3 sorry, there are newer releases, some of which i had issues with but may have been corrected.
-----Original Message-----
From: Tim Alsop [mailto:Tim.Alsop at CyberSafe.Ltd.UK]
Sent: Thursday, October 20, 2005 11:31 AM
To: Chapman, Kyle; cyrus-sasl at lists.andrew.cmu.edu; jorma.heikkuri at pp.inet.fi; walter+sasl at efrei.fr
Subject: RE: SASL on AIX 5.x
Kyle,
That is good news. How do I install a new version of libtool ? e.g. where is it best to download from, and what steps do I perform so that SASL uses the new libtool ?
Cheers, Tim
_____
From: Chapman, Kyle [mailto:Kyle_Chapman at G1.com]
Sent: 20 October 2005 16:29
To: Tim Alsop; cyrus-sasl at lists.andrew.cmu.edu; jorma.heikkuri at pp.inet.fi; walter+sasl at efrei.fr
Subject: RE: SASL on AIX 5.x
i just built 2.1.21 on 5.2 (shared). i have vac7, and i have done it with 6 as well. i run configure as normal, but after this is done, use a different ver of libtool to compile.
1.4.8 i used this past run. i didnt have to edit any of the config env of sasl either.
-----Original Message-----
From: Tim Alsop [mailto:Tim.Alsop at CyberSafe.Ltd.UK]
Sent: Thursday, October 20, 2005 4:35 AM
To: cyrus-sasl at lists.andrew.cmu.edu; jorma.heikkuri at pp.inet.fi; Chapman, Kyle; walter+sasl at efrei.fr
Subject: SASL on AIX 5.x
Hello,
I wondered if you could help me ?
I noticed from some posts to the Cyrus SASL mailing list that many people have had difficultly compiling SASL 2.1.x on AIX 5.x. I am also trying to do this, but using SASL 2.1.21. Do you have any clues how to make SASL compile on AIX 5 ? I am using IBM AIX VisualAge C compiler 6.0.
So, far I have edited the config/ltconfig file (to cause configure decide it can create shared libraries). The changes I made are :
-deplibs_check_method='unknown'
+deplibs_check_method='pass_all'
Then, when I run configure, I get output which looks good, then I run make, and get :
% make
make all-recursive
Making all in include
source='makemd5.c' object='makemd5.o' libtool=no depfile='.deps/makemd5.Po' tmpdepfile='.deps/makemd5.TPo' depmode=aix /bi
n/sh ../config/depcomp xlc_r -DHAVE_CONFIG_H -I. -I. -I.. -I/home/talsop/source/external/cyrussasl/../../toolkits/devpack/securi
ty-tk/include -I/krb5/include -D__aix -D__aix -I/krb5/appsec-sdk/include -g -c `test -f 'makemd5.c' || echo './'`makemd5.c
/bin/sh ../libtool --mode=link xlc_r -g -blibpath:/krb5/external/sasl/lib:/krb5/external/ldap/lib:/krb5/appsec-rt/lib:/k
rb5/lib:/usr/lib -L/home/talsop/source/external/cyrussasl/../../toolkits/devpack/security-tk/lib -L/home/talsop/source/external/cyru
ssasl/../../common/k542/lib -L/krb5/lib -o makemd5 makemd5.o
mkdir .libs
xlc_r -g -blibpath:/krb5/external/sasl/lib:/krb5/external/ldap/lib:/krb5/appsec-rt/lib:/krb5/lib:/usr/lib -L/home/talsop/source/exte
rnal/cyrussasl/../../toolkits/devpack/security-tk/lib -L/home/talsop/source/external/cyrussasl/../../common/k542/lib -L/krb5/lib -o
makemd5 makemd5.o
rm -f md5global.h
./makemd5 md5global.h
Target "all" is up to date.
Making all in sasldb
source='allockey.c' object='allockey.lo' libtool=yes depfile='.deps/allockey.Plo' tmpdepfile='.deps/allockey.TPlo' depmode
=aix /bin/sh ../config/depcomp /bin/sh ../libtool --mode=compile xlc_r -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I
/home/talsop/source/external/cyrussasl/../../toolkits/devpack/security-tk/include -I/krb5/include -D__aix -D__aix -I/krb5/appsec-sdk
/include -g -c -o allockey.lo `test -f 'allockey.c' || echo './'`allockey.c
rm: illegal option -- W
Usage: rm [-firRe] [--] File ...
xlc_r -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I/home/talsop/source/external/cyrussasl/../../toolkits/devpack/securit
y-tk/include -I/krb5/include -D__aix -D__aix -I/krb5/appsec-sdk/include -g -c allockey.c -Wc,-M
"allockey.c", line 190.28: 1506-280 (E) Function argument assignment between types "const char*" and "const unsigned char*" is not a
llowed.
mv -f -Wc,-M.o allockey.o
mv: illegal option -- W
Usage: mv [-i | -f] [-E{force|ignore|warn}] [--] src target
or: mv [-i | -f] [-E{force|ignore|warn}] [--] src1 ... srcN directory
make: 1254-004 The error code from the last command is 1.
Stop.
make: 1254-004 The error code from the last command is 1.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
As you can see from the above, for some reason rm and mv are failing because of invalid options, so it seems that the compiler options are being interpreted as a filename, for some strange reason ? Does anybody have any ideas what might cause this ?
Thanks, Tim
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.
NOTICE: This E-mail may contain confidential information. If you are not
the addressee or the intended recipient please do not read this E-mail
and please immediately delete this e-mail message and any attachments
from your workstation or network mail system. If you are the addressee
or the intended recipient and you save or print a copy of this E-mail,
please place it in an appropriate file, depending on whether
confidential information is contained in the message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.andrew.cmu.edu/mailman/private/cyrus-sasl/attachments/20051020/bb6451bc/attachment-0001.html
More information about the Cyrus-sasl
mailing list