Eric Young wrote:

> On Wed, 27 May 1998, Tim Pushor wrote:
> > 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 stuffed up in several places.
>
> > gcc -o ssleay -DMONOLITH -I../include (..)
> > cx86-out.o: Undefined symbol `CAST_S_table0' referenced from text
> > segment
>
> First, my perl scripts that generated assember were not putting in the leading
> underscore needed for a.out based systems (like FreeBSD).

Ahh. I can live with this for a while (like I have a choice :)

>
>
> > 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
>
> Ah, I have not tested the 'make SSLeay from 2 files' option for some time,
> and I have not got everything working correctly.  It will be tested before
> 0.9.1.
>
> > Looking at the header files I do definately see two different prototypes
> > and
>
> Cleaned up for 0.9.1
>
> > 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.
>
> It is my stuffup.  The duplicate definitions in bn.h and bn_locl.h have been
> removed.  I'd probably advise holding off on the 'build from 2 files'
> type of building shared libraries for a little, until the next version which
> should be out in a few weeks.
>
> The slightly harder way to make a shared library with the existing makefile
> is to set the correct compiler flags,
> do a standard make (which make break when the applications are being linked),
> then use 'ar' to pull the archives apart, into a seperate directory, and
> then link into a shared libarary.  Unfortunatly you will probably have to
> know what you are doing to do this :-).
>

Well, I may not know what I am doing with the Internals of SSLeay, but am not a
newbie to programming.

That was a great idea, and it worked just fine. I now have shared libraries with
0.9.0 under FreeBSD!

Thanks for the help,
Tim

(Sorry if this comes out MHTML, I am having problems with Communicator/FreeBSD)


+-------------------------------------------------------------------------+
| Administrative requests should be sent to [EMAIL PROTECTED] |
| List service provided by Open Software Associates, http://www.osa.com/  |
+-------------------------------------------------------------------------+

Reply via email to