Re: Solaris 8 cyrus-imspd-v1.6a3 can't make lib/prot.o

[Eric S. Pulley]

There is a patch to authenticate via the imap server as well. Which is what I'm using succefully. Only down side is you have to use plain text and no ssl on the ismp account. IMAP can still use whatever AUTH your server supports. I just only allow ismp connection from inside my firewall.

--On Friday, February 7, 2003 8:39 +1100 Peter Lawler <[EMAIL PROTECTED]> wrote:

Hi there Glo,
I've got a home brewed Solaris x86 box I thought I'd give it a whirl
for you. I'm running a self-compiled gcc 3.2.1, that seems to be
going OK - it's down cyrus-imap & sasl and apache2.xx so far, so I
think it's OK (haven't had a chance to get the GCC test suite from
work yet, seeing 'I don't need it'), long story. But I digress...

Current working directory /usr/local/src/cyrus-imspd-v1.6a3/lib

I don't know if this is relevant, but cyrus-sasl-2.1.10 was
configured

Well, I was scratching my head too. I started falling over building
imclient:
imclient.c: In function `imclient_connect':
imclient.c:288: warning: passing arg 5 of `sasl_client_new' from
incompatible pointer type
imclient.c:288: too few arguments to function `sasl_client_new'
imclient.c: In function `imclient_input':
imclient.c:676: warning: passing arg 4 of `sasl_decode' from
incompatible pointer type
imclient.c: In function `imclient_processoneevent':
imclient.c:995: warning: passing arg 4 of `sasl_encode' from
incompatible pointer type
imclient.c: In function `interaction':
imclient.c:1163: warning: passing arg 1 of `memset' discards
qualifiers from pointer target type
imclient.c: In function `imclient_authenticate_sub':
imclient.c:1226: `SASL_IP_REMOTE' undeclared (first use in this
function) imclient.c:1226: (Each undeclared identifier is reported
only once imclient.c:1226: for each function it appears in.)
imclient.c:1234: `SASL_IP_LOCAL' undeclared (first use in this
function) imclient.c:1252: warning: passing arg 4 of
`sasl_client_start' from incompatible pointer type
imclient.c:1252: warning: passing arg 5 of `sasl_client_start' from
incompatible pointer type
imclient.c:1252: warning: passing arg 6 of `sasl_client_start' from
incompatible pointer type
imclient.c:1252: too many arguments to function `sasl_client_start'
imclient.c:1295: warning: passing arg 5 of `sasl_client_step' from
incompatible pointer type

Then I started looking at the dates on this thing. It's 2000. I
*suspect* imsp may not be compatible with SASL2...... The reasoning
was in the porting the app document doc/appconvert.html, which says:
"The SASL_IP_REMOTE and SASL_IP_LOCAL properties are now
SASL_IPLOCALPORT and SASL_IPREMOTEPORT and take strings"

Hmmmm.... Oh dear, it's late. I'm writing offline. I think I might go
sleep some :-)

Pete.

------------------------
|     Eric S. Pulley     |
| Sr. Unix Administrator |
|   Hamilton Partners    |
|    +1.707.431.4300     |
|  <[EMAIL PROTECTED]>   |
------------------------

msg10980/pgp00000.pgp
Description: PGP signature