When building OpenSSL 1.1.0 pre4 on Solaris Sparc for 64 Bits I get an
error, because before building crypto/bn/sparcv8plus.o first generates
crypto/bn/asm/sparcv8plus.s from crypto/bn/asm/sparcv8plus.S with the
following command
gcc -E crypto/bn/asm/sparcv8plus.S >
Commit 674d5858df6cd3dc5cafa25875861f4742d64608, merged to master. Closing
ticket.
Cheers,
Richard
Vid Sat, 19 Mar 2016 kl. 13.38.57, skrev rainer.j...@kippdata.de:
> Hi Richard,
>
> Am 19.03.2016 um 12:49 schrieb Richard Levitte via RT:
> > So I'm wondering, what happens if you apply the
Hi Richard,
Am 19.03.2016 um 12:49 schrieb Richard Levitte via RT:
> So I'm wondering, what happens if you apply the attached patch?
Works like a charm, tested on Solaris 10 Sparc doing a 32bit build and a
64bit build. The intermediate ".s" (lower case) file no longer gets
generated and
Hi Richard,
Am 19.03.2016 um 12:49 schrieb Richard Levitte via RT:
So I'm wondering, what happens if you apply the attached patch?
Works like a charm, tested on Solaris 10 Sparc doing a 32bit build and a
64bit build. The intermediate ".s" (lower case) file no longer gets
generated and
So I'm wondering, what happens if you apply the attached patch?
Vid Sat, 19 Mar 2016 kl. 11.02.09, skrev levitte:
> Hmmm...
>
> Actually, I'm thinkg that src2obj() should check if the original file
> exists as
> given before changing .S to .s... That should work, since we're always
> generating
Hmmm...
Actually, I'm thinkg that src2obj() should check if the original file exists as
given before changing .S to .s... That should work, since we're always
generating 'foo.s' from 'asm/foo.S' (or 'asm/foo.pl', but that's not applicable
here)... The directory difference should make it safe.
