Use ./Configure NetBSD-x86 to get SSLeay compiled under FreeBSD 2.2.6.
I have the same setup here.
Although I'm trying to use it together with stunnel and I'm having trouble
to get stunnel working. I'm using stunnel-2.0 and try to get it working with
imap: /usr/sbin/stunnel 993 imapd. So far so good. When I try to connect
with SSL enabled netscape I get the certificate presented ok but then the
browser goes: "Netscape is unable to connect to the server at the location
you have specified. The server may be down or busy". In the syslog everything
looks ok:
May 28 06:48:16 forsete stunnel[2444]: imapd connected from 192.168.174.2:39138
The client is Netscape Communicator 4.05 running on a Sun Sparc Solaris 2.5.1
machine.
Anyone has this setup working?
Rainer.
> Hello,
>
> (Apologizing in advance for the long winded post)
>
> I am attempting to build SSLeay 0.9.0 under FreeBSD 2.2.6. The build
> fails
> using the defaults. Here is what I do, and what happens:
>
> (I have perl 5 installed as /usr/bin/perl)
> perl /util/perlpath.pl /usr/bin
> ./Configure FreeBSD
> make
>
> The build fails:
>
> gcc -o ssleay -DMONOLITH -I../include (..)
>
> cx86-out.o: Undefined symbol `CAST_S_table0' referenced from text
> segment
> cx86-out.o: Undefined symbol `CAST_S_table1' referenced from text
> segment
> cx86-out.o: Undefined symbol `CAST_S_table2' referenced from text
> segment
> cx86-out.o: Undefined symbol `CAST_S_table3' referenced from text
> segment
> cx86-out.o: Undefined symbol `CAST_S_table0' referenced from text
> segment
>
> <lots more of these>
>
> Seems that somehow the tables defined in crypto/cast/cast_s.h are not
> finding their way into the lib for some reason.. Editing Makefile.ssl
> to use the C version of the cast stuff clears that up..
>
> So now I am trying to create a shared library and have used the linux
> script as a template. I did this with the 0.8.x version of SSLeay with
> no
> problems, but I must have been smarter back then :).. I define TERMIOS,
> change -DELF to -DOUT. At this point I figure it should compile, but
> maybe not link, so I try to compile and get lots of redifinition
> warnings
> and errors:
>
> compiling bignum assember
> compiling des assember
> compiling blowfish assember
> compiling cast assember
> compiling rc4 assember
> compiling md5 assember
> compiling sha1 assember
> compiling libcrypto
> In file included from crypto/crypto.c:520:
> crypto/sha/sha_dgst.c:88: warning: `M_c2nl' redefined
> crypto/sha/sha1dgst.c:100: warning: this is the location of the previous
> definition
> crypto/sha/sha_dgst.c:89: warning: `M_p_c2nl' redefined
> crypto/sha/sha1dgst.c:101: warning: this is the location of the previous
> definition
> crypto/sha/sha_dgst.c:90: warning: `M_c2nl_p' redefined
> crypto/sha/sha1dgst.c:102: warning: this is the location of the previous
> definition
> crypto/sha/sha_dgst.c:91: warning: `M_p_c2nl_p' redefined
> crypto/sha/sha1dgst.c:103: warning: this is the location of the previous
> definition
> crypto/sha/sha_dgst.c:92: warning: `M_nl2c' redefined
> crypto/sha/sha1dgst.c:104: warning: this is the location of the previous
> definition
> In file included from crypto/bn/bn_add.c:61,
> from crypto/crypto.c:221:
> crypto/bn/bn_lcl.h:183: conflicting types for `bn_add_words'
> include/bn.h:367: previous declaration of `bn_add_words'
> crypto/bn/bn_add.c: In function `bn_qadd':
> In file included from crypto/crypto.c:221:
> crypto/bn/bn_add.c:139: warning: passing arg 3 of `bn_add_words' makes
> integer from pointer without a cast
> crypto/bn/bn_add.c:139: too many arguments to function `bn_add_words'
> crypto/bn/bn_add.c:139: void value not ignored as it ought to be
> crypto/bn/bn_sqr.c: In function `BN_sqr':
> In file included from crypto/crypto.c:236:
> crypto/bn/bn_sqr.c:110: warning: passing arg 3 of `bn_add_words' makes
> integer from pointer without a cast
> crypto/bn/bn_sqr.c:110: too many arguments to function `bn_add_words'
> crypto/bn/bn_sqr.c:116: warning: passing arg 3 of `bn_add_words' makes
> integer from pointer without a cast
> crypto/bn/bn_sqr.c:116: too many arguments to function `bn_add_words'
> crypto/des/read_pwd.c: In function `des_read_pw':
> In file included from crypto/crypto.c:277:
>
> (...)
>
> Looking at the header files I do definately see two different prototypes
> and
> the only thing I can come up with is that maybe using X86 assembler the
> prototypes would be different, but then why would the others be
> included?
> I'm confused.
>
> Can someone who knows this system better than me help?
>
> Thanks,
> Tim
>
> +-------------------------------------------------------------------------+
> | Administrative requests should be sent to [EMAIL PROTECTED] |
> | List service provided by Open Software Associates, http://www.osa.com/ |
> +-------------------------------------------------------------------------+
+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/ |
+-------------------------------------------------------------------------+
