I already answered this once, but it didn't come through for some
reason...
+ sx6, cc:-g -DTERMIOS::(unknown):::SIXTY_FOUR_BIT DES_INT:::,
No optimization? Not even lousy -O?
-g overrides any optimization you give,
Yes, that's what normally happens...
and i think there's a problem
Config was adding 386 to the Configure line causing the build
to fail on the assembler modules.
in what way?
UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg
Would it work if you add b to xchg mnemonic, i.e. make it look xchgb
1)I didn't give any preference to aix-cc;
But you've suggested to change it:-)
I just changed
in config script the default CC=gcc to CC=cc for AIX case only.
Is vendor compiler optional on AIX? Because if it is, then you've got to
test if cc is actually present. Normally it's done by passing
Have the 5 section look something like
--
5)
if [ `echo x$VERSION | sed -e 's/\..*//'` = x7 ]; then
echo i586-sco-unixware7; exit 0
elif [ `echo x$VERSION | sed -e 's/\..*//'` = x8 ]; then
echo
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote:
Config was adding 386 to the Configure line causing the build
to fail on the assembler modules.
in what way?
UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg
Would it work
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote:
Config was adding 386 to the Configure line causing the build
to fail on the assembler modules.
in what way?
UX:as: ERROR: asm/sx86-elf.s:35:invalid register for instruction: %al in xchg
Would it work
To summarize. I'm hardcoding i586 to all Caldera/SCO targets. And
according to RT#460 we also should get rid of -lresolv on those
platforms, right? A.
And yes, get rid of -lresolv on the sco5 (OpenServer 5) targets.
The question also is if it's needed even in unixware-2.* lines. As
On Fri, Jan 17, 2003, Himanshu Soni wrote:
128 Bit rc2 also fails on windows 98. Openssl can successfully decrypt
the message on windows 98.
Hmmm, strange. Have you tried an alternative certificate for the Win98
recipient? Also what does a signed message look like for that certificate, in
On Sat, 18 Jan 2003, Andy Polyakov via RT wrote:
Have the 5 section look something like
--
[snip]
Updated config is in both HEAD and 0.9.7-stable CVS. Please verify and
reply so that the ticket can be resolved. A.
UX:sh (./config): ERROR: ./config: Syntax error at line 442: `fi'
Did you build a debug version of OpenSSL to link against for the debug
build? This isn't handled automatically and you need to change it so it
picks up and uses the debug libraries.
Nope. that would explain it. criss-crossing MS multi-threaded libs is
always a problem. I was using my debug
10 matches
Mail list logo
