I got two replies :-
Richard Levitte said :
Richard> Well, it looks like Compaq C will just ignore -fPIC when it
compiles,
Richard> and try to pass it on to ld when linking is going on. However,
Richard> there's no support for -fPIC anywhere in True64.
[ Thanks Richard: I have no idea *what* PIC/pic is about, so I'll just let
this slip by me :-( ]
Richard> If you check the
Richard> manual for ld, you'll probably find a few lines about '-f fil',
where
Richard> the filling is expected to be a 4-byte hex constant.
Well you're quite right; the ld man page says :
-f fill
Set the fill pattern for "holes" within an output section. The argu-
ment fill is a four-byte hexadecimal constant.
But what I don't understand is why you're talking about a problem with
"-fPIC" when my compilation objected to "-std1" ...
Richard> My suggestion: don't configure with -fPIC on True64.
Anyway, I followed your suggestion, configuring with "./config no-idea", and
my compilation completed OK, and "make test" has run OK.
Since the "-fPIC" parameter is documented in the MOD_SSL documentation as
being required when building OpenSSL if we want to build MOD_SSL as an
Apache DSO module, does this mean I can't run Apache/MOD_SSL configured with
dynamic shared modules on a Digital Unix platform ?
====================< cut >======================
Meanwhile, Michael Barnes emailed me directly to say :
Michael> try this:
Michael>
Michael> cc -o openssl openssl.o verify.o asn1pars.o req.o dgst.o dh.o
dhparam.o
Michael> enc.o passwd.o gendh.o errstr.o ca.o pkcs7.o crl2p7.o crl.o rsa.o
dsa.o
Michael> dsaparam.o x509.o genrsa.o gendsa.o s_server.o s_client.o speed.o
s_time.o
Michael> apps.o s_cb.o s_socket.o app_rand.o version.o sess_id.o ciphers.o
nseq.o
Michael> pkcs12.o pkcs8.o spkac.o smime.o rand.o -L. -L.. -L../.. -L../../..
-lssl
Michael> -lcrypto
Michael>
Michael> apparently Digital unix's cc cannot correctly tell between a link
Michael> and a compile. The above command should work, but I do not have
Michael> access to a Digital unix machine right now.
Thanks Michael. I tried this command hands-on and it worked. Looking at
your cc call, you're supplying all the same input modules as the distro
does, but omitting most of the commandline switches including "-fPIC" *and*
"-stdl". I guess that will avoid any complaining about either of those
options, but what is the effect on the compilation of omitting the other
switches (e.g. -DMONOLITH, -DNO_IDEA, -tune, -readonly-strings) ?
And should I submit bugs on all this ? (Or is Digital Unix support
"experimental" ?)
> Nick
> Systems Team, EDS Healthcare, Bristol, UK
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
