Try out openssl-SNAP-20030109 as it becomes available or 'cvs checkout'.
UnixWare 2.x and SCO3 remain without assembler support. If you feel
emotionally attached to these two, I'd suggest to trade assembler
support for a comment in ./Configure which says that
<[EMAIL PROTECTED]> is the one to talk
On Wed, 8 Jan 2003, Andy Polyakov wrote:
> > The existing rules (in HEAD) work fine for UnixWare 7.x, OpenUNIX 8.0.0,
> > & SCO Open Server 5 (current shipping products)
>
> Great! Next and final question is why unixware-7, unixware-7-pentium,
> unixware-7-pentium_pro, etc.? The point being is th
> > Options:
> >
> > 1. Move *-elf.[os] one level up, e.g.:
> >
> > dx86-elf.s: asm/des-586.pl ../perlasm/x86asm.pl ../perlasm/cbc.pl
> > (cd asm; $(PERL) des-586.pl elf $(CFLAGS) > ../dx86-elf.s)
>
> This option didn't work out very well.
> ...
> making all in crypto/md5...
> cc -
On Tue, 7 Jan 2003, Andy Polyakov wrote:
> > > > > The cc on UnixWare 2.x doesn't handle -o asm/xx86-elf.o
> > > > > It just creates it in the curent directory.
> > >
> > > ??? Does it mean that cc driver effectively ignores -o option? Or does
> > > it mean that make doesn't pass -o option to cc d
> > > > The cc on UnixWare 2.x doesn't handle -o asm/xx86-elf.o
> > > > It just creates it in the curent directory.
> >
> > ??? Does it mean that cc driver effectively ignores -o option? Or does
> > it mean that make doesn't pass -o option to cc driver when compiling .s
> > files? If former, does i
On Mon, 6 Jan 2003, Andy Polyakov wrote:
> > > The cc on UnixWare 2.x doesn't handle -o asm/xx86-elf.o
> > > It just creates it in the curent directory.
>
> ??? Does it mean that cc driver effectively ignores -o option? Or does
> it mean that make doesn't pass -o option to cc driver when compilin
> > The cc on UnixWare 2.x doesn't handle -o asm/xx86-elf.o
> > It just creates it in the curent directory.
??? Does it mean that cc driver effectively ignores -o option? Or does
it mean that make doesn't pass -o option to cc driver when compiling .s
files? If former, does it apply to .s files onl
On Fri, 3 Jan 2003, Tim Rice wrote:
> On Fri, 3 Jan 2003, Andy Polyakov wrote:
>
[snip]
> The assembler modules compile fine on UnixWare. I'll try and
> test SCO OpenServer 5 this weekend.
The assembler modules compile fine on SCO OpenServer 5 too.
>
> A couple of problems.
>
> The cc on Unix
On Fri, 3 Jan 2003, Andy Polyakov wrote:
> > It looks like the PIC changes to crypto/perlasm/x86unix.pl break
> > on non gcc compilers.
>
> ... on SCO5/UnixWare/OpenUnix platforms...
>
> Test ftp://ftp.openssl.org/snapshot/openssl-SNAP-20030103.tar.gz as it
> becomes
> It looks like the PIC changes to crypto/perlasm/x86unix.pl break
> on non gcc compilers.
... on SCO5/UnixWare/OpenUnix platforms...
Test ftp://ftp.openssl.org/snapshot/openssl-SNAP-20030103.tar.gz as it
becomes available. Well, I haven't added ${x86_elf_asm} to
SCO5/UnixWare/OpenUni
> It looks like the PIC changes to crypto/perlasm/x86unix.pl break
> on non gcc compilers.
First of all it's an assembler issue, not compiler. And I don't think
it's GNU vs. vendor assembler issue, ...
> UX:acomp: ERROR: "asm/dx86unix.cpp", line 122: invalid
First, this should NOT hold up 0.9.7
I'm using assembly on targets that are not yet supported.
It looks like the PIC changes to crypto/perlasm/x86unix.pl break
on non gcc compilers.
...
making all in crypto/des...
cc -E -DSOL \
`(echo -I.. -I../.. -I../../in
12 matches
Mail list logo
