On Tue, Sep 28, 1999, [EMAIL PROTECTED] wrote:
> Full_Name:
> Version: 2.4.4
> OS: Slackware-current
> Submission from: dns0.prestoncoll.ac.uk (194.238.8.2)
>
> hmm, very related to bug 291!
> when using the "The flexible APACI-only way", everything works fine until here:
>
> ===> src/modules/ssl
> -DSSL_COMPAT -I/usr/src/openssl-0.9.4/include -DMOD_SSL_VERSION=\"2.4.4\"
> ssl_engine_mutex.c
> ssl_engine_mutex.c: In function `ssl_mutex_sem_create':
> ssl_engine_mutex.c:293: incompatible type for argument 4 of `semctl'
> ssl_engine_mutex.c:302: incompatible type for argument 4 of `semctl'
> ssl_engine_mutex.c: In function `ssl_mutex_sem_remove':
> ssl_engine_mutex.c:334: incompatible type for argument 4 of `semctl'
> make[4]: *** [ssl_engine_mutex.o] Error 1
Err... now I'm more than confused. semctl(2) is a var-args functions which has
only 3 defined arguments (plus their types). So how can this Slackware beast
complain about the forth argument? I'm crazy now or what?
> if you need any additional information, email me
Yes, I need more information. How is semctl defined in your system headers?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
