grab the developer studio workspace and all of the project
files off of my homepage - the s_client (and all of the standalone apps)
project has all of the correct settings (from compiler options to
library resolution) applied. http://www.iconsinc.com/~agray/ossldev/
Andrew
Marcus Carey wrote:
&
>I intend to ultimately use SNACC as a compiler but using its template
>output as the input to a converter to OpenSSL template format.
yea - the one i noticed was the bitstr start. I'm having a hell of a
time doing cvs updates recently - very poor connexns from home.
have you started this - i.e.
>2 or 3
your time of course ;-)
> And in any case, I personally wouldn't trust a shared OpenSL library
> just yet. There are just too many things that are about to change...
i've seen - i'm playing hell on keeping up on what's going on. You and
Geoff on the engine work as well as Steve starti
Always watch for -shared and the -expect_unresolved "*" for DigUnix ld
options. I was building api libraries against ssleay for Netscape
server 1-->2.x along time ago (3-5 yrs ago) and as i remember this was
necessary.
> I'm now pressing ahead on building OpenSSL/Apache/Mod_SSL *with* DSO Apache
Boyce, Nick wrote:
>
> Richard Levitte wrote :
>
> > nick.boyce> But what I don't understand is why you're talking about a
> > nick.boyce> problem with "-fPIC" when my compilation objected to
> > nick.boyce> "-std1" ...
> >
> > Ah. Well, I'll do some qualified guesses: suppose that the command
n the ssl negotiation - remember source code
is self-documenting ;-)
The workspace that is floating around on the lists will be superceded
this weekend with one with alot of "bug" fixes and lots of
compiler/linker flag corrections.
Andrew
--
openssl devstu
