Missing libraries when making c-client

[Jamie Ostrowski]

>
>
>    I am having some trouble installing imap from source. I am building a
> machine for my boss who *insists* that I cannot use anything from the
> ports collection on the machine, so I can't use the imap port.
>
>    The build is failing, and it seems as though it can't find some openssl
> include files, judging from the errors I am getting.
>
>    This is on a stock 4.11 system. When I untar the imap-2004c1 source, I
> read the readme doc, and I ran
>
> make bsf
>
> since it is a FreeBSD install. It will not compile, though. Here is where
> it is failing:


Here is something higher up in the make output that looks like it may be a
clue:

Building with SSL
ln -s ssl_unix.c osdepssl.c
echo -I/usr/local/ssl/include -I/usr/local/ssl/include/openssl
-DSSL_CERT_DIRECTORY=\"/usr/local/ssl/certs\"
-DSSL_KEY_DIRECTORY=\"/usr/local/ssl/certs\" >> OSCFLAGS
echo "  ssl_onceonlyinit ();" >> linkage.c
echo -L/usr/local/ssl/lib -lssl -lcrypto  >> LDFLAGS


It seems to be setting info in the files OSCFLAGS and LDFLAGS to
/usr/local/ssl, and I don't have any /usr/local/ssl directory, and I am
unsure how this can be corrected properly.







>
> Building with SSL and plaintext passwords disabled unless SSL/TLS
> echo "  mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >>
> linkage.c
> cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c
> Building OS-dependent module
> If you get No such file error messages for files x509.h, ssl.h,
> pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL
> is not installed on your system. Either install OpenSSL first
> or build with command: make bsf SSLTYPE=none
> `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c
> osdep.c:138: x509.h: No such file or directory
> osdep.c:139: ssl.h: No such file or directory
> osdep.c:141: pem.h: No such file or directory
> osdep.c:142: buffer.h: No such file or directory
> osdep.c:143: bio.h: No such file or directory
> osdep.c:144: crypto.h: No such file or directory
>
>
>   etc etc etc...
>
>
> In the Makefile, under the "bsf" target, we see that the path to the stock
> openssl libraries in FreeBSD is declared:
>
> bsf bso:        an
>         $(BUILD) BUILDTYPE=$@ \
>         SPECIALS="GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl
> SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private LOCKPGM=/usr/sbin/mlock"
>
>
>
>    ...and an ls of /usr/include/openssl does include x509.h, ssl.h, pem.h,
> etc.
>
>     Does anyone have any explanation for why it isn't finding those files?
> Any direction I can go from here? I would rather not build an additional
> openssl package from a source tree as I would like to just use what is on
> the system. It would make things cleaner (fewer moving parts) when
> cvsupping and building world, etc. I would prefer to use the native
> libraries.
>
>
>    Thanks,
>
>    - Jamie
>
>
>
>
>
> The Moon is Waning Gibbous (100% of Full)
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>

The Moon is Waning Gibbous (100% of Full)