Re: SHA512

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: SHA512

Tim Rice
On Sat, 21 May 2005, Tim Rice wrote:

>
> It looks like SHA512 requires a 64bit data type.
> So on older platforms that do not have long long support,
> you get errors like
> ....
> making all in crypto/sha...
> gmake[2]: Entering directory `/var/local/src/libs/openssl-0.9.8/crypto/sha'
> cc -I.. -I../.. -I../../include -DOPENSSL_THREADS -Kthread -DFILIO_H
> -DNO_STRINGS_H   -c  sha_dgst.c
> UX:acomp: ERROR: "../../include/openssl/sha.h", line 172: invalid type
> combination
> UX:acomp: ERROR: "../../include/openssl/sha.h", line 173: invalid type
> combination
> UX:acomp: ERROR: "../../include/openssl/sha.h", line 175: invalid type
> combination
> gmake[2]: *** [sha_dgst.o] Error 1
> ....
>

This problem still exists with the OpenSSL_0_9_8-stable branch
pulled Mon May 30 19:47:25 PDT 2005.


--
Tim Rice Multitalents (707) 887-1469
[hidden email]


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: SHA512

Andy Polyakov
>> `/var/local/src/libs/openssl-0.9.8/crypto/sha'
>> cc -I.. -I../.. -I../../include -DOPENSSL_THREADS -Kthread -DFILIO_H
>> -DNO_STRINGS_H   -c  sha_dgst.c
>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 172: invalid type
>> combination
>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 173: invalid type
>> combination
>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 175: invalid type
>> combination
>> gmake[2]: *** [sha_dgst.o] Error 1
>> ....
>>
>
> This problem still exists with the OpenSSL_0_9_8-stable branch
> pulled Mon May 30 19:47:25 PDT 2005.

Can you confirm that problem persists even if you './config
no-sha512'(*)? If you can confirm this, then you would have to speculate
why does it happen in your opinion. A.

(*) it will advice to run 'make depend', it might fail with your make
[working on it], but it's safe to compile without running 'make depend'.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: SHA512

Tim Rice
On Tue, 31 May 2005, Andy Polyakov wrote:

>>> `/var/local/src/libs/openssl-0.9.8/crypto/sha'
>>> cc -I.. -I../.. -I../../include -DOPENSSL_THREADS -Kthread -DFILIO_H
>>> -DNO_STRINGS_H   -c  sha_dgst.c
>>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 172: invalid type
>>> combination
>>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 173: invalid type
>>> combination
>>> UX:acomp: ERROR: "../../include/openssl/sha.h", line 175: invalid type
>>> combination
>>> gmake[2]: *** [sha_dgst.o] Error 1
>>> ....
>>>
>>
>> This problem still exists with the OpenSSL_0_9_8-stable branch
>> pulled Mon May 30 19:47:25 PDT 2005.
>
> Can you confirm that problem persists even if you './config no-sha512'(*)? If
> you can confirm this, then you would have to speculate why does it happen in
> your opinion. A.

Adding no-sha512 to the config line is not enough.
I also have to add -DOPENSSL_NO_SHA512

Now the UnixWare 2.03 box bombs at
...
making all in crypto/pqueue...
         cc -I.. -I../.. -I../../include -DOPENSSL_THREADS -Kthread -DOPENSSL_NO_
SHA512 -DFILIO_H -DNO_STRINGS_H -c pqueue.c
UX:acomp: ERROR: "./pqueue.h", line 73: Syntax error before or at: BN_ULLONG
UX:acomp: ERROR: "./pqueue.h", line 73: cannot recover from previous errors
*** Error code 1 (bu21)
...

Another "no 64bit data type" error. (PQ_64BIT)

I don't see any way to disable that section.

Maybe at some point you just want to say
"We no longer support older compilers that do not have some 64bit data type".

I'd be OK with that (OpenSSH is already there).
It would just need to be documented and then I'd just have to patch
Configure to remove a couple of cc targets and add gcc targets.


--
Tim Rice Multitalents (707) 887-1469
[hidden email]


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [hidden email]
Automated List Manager                           [hidden email]