Well here's a nice ten-liner that will undo the recent damage to HPUX
32 bit builds using HP's compilers/linkers;
+ cc -b -Wl,-B,symbolic,+vnocompatwarnings,-z,+h,libssl.sl.0.9.7 -o
libssl.sl.0.9.7 -Wl,-Fl,libssl.a -ldld
chmod: can't access libssl.sl.0.9.7
Does it mean that it succeeded to build libcrypto.sl, but not libssl.sl?
If yes, could you find out why? I won't be surprised if it also answers
your questions:-) For the record, I can *not* reproduce any of the
claims in this report and disagree with strong formulations such as
"damage" and so on.
WTF is it about? Well, used to link using ld directly, now we are
passing through cc.
Yes [and for a reason], and it *was* thoroughly tested on 32-bit HP-UX.
But without splitting -Wl,-Fl from libssl.a with
a space,
??? 'cc -b -Wl,-Fl,libssl.a ...' should be/is translated to 'ld -b -Fl
libssl.a ...' by cc. Comma in cc -Wl stands for space in ld line. Add -v
flag to the above command line and verify. If your cc fails, then HP
ought to have patch [or upgrade].
Secondly, once we remove the space,
You contradict yourself: first you say "space is required," and here you
say "space has to be removed." Make up your mind:-)
we crash out with
/usr/ccs/bin/ld: CODE_ONE_SYM fixup to non-code subspace in file
/opt/langtools/lib/crt0.o - shared library must be position
independent. Use +z or +Z to recompile.
'cc -b ...' should be/is translated to 'ld -b ...' *without* crt0.o. Add
-v flag to the above command line and test with and without -b.
http://mail.gnome.org/archives/gtk-list/1999-March/msg00704.html reports
similar issues, with no resolution on how-to-exclude crt0.o from the 'cc'
flavor,
They were using -Wl,-b, while you're expected to pass -b directly to cc.
Finally -b +s disappeared between 0.9.7e and 0.9.7i,
??? You yourself have presented evidence that -b is there [command line
above]. As for +s, it's used to link executables [where it's actually
effective], but not to lib*.sl [where it does nothing anyway]. Verify
the application link command line for presence of +s.
but it certainly is needed on 32 bit builds.
And it's there for me. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
