On 2005.05.31 at 14:40:46 +0200, Andy Polyakov via RT wrote:
> According to our records, your request has been resolved. If you have any
> further questions or concerns, please respond to this message.
Bug 1084 was resolved with following diagnositics
> Not OpenSSL problem. Explicitly mentioned in ./PROBLEMS, case dismissed
But I cannot find anything related to my situation:
solaris64-sparcv9-gcc, gcc version 3.3, RIPEMD160 algorithm.
As far as I can understand, each problem description in the PROBLEMS
file starts with asterisk at first position of line.
grep -n '^\*' PROBLEMS
1:* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X.
42:* Parallell make leads to errors
51:* Bugs in gcc 3.0 triggered
66:* solaris64-sparcv9-cc SHA-1 performance with WorkShop 6 compiler.
74:* Problems with hp-parisc2-cc target when used with "no-asm" flag
93:* Problems building shared libraries on SCO OpenServer Release 5.0.6
Obvoisly, problem mentioned on line 66 is irrelevant. Problem, mentioned
in line 51 seems to not to be relevant to gcc 3.3 too.
Please point me out line number which describes my problem.
> Bug 1084 was resolved with following diagnositics
>>Not OpenSSL problem. Explicitly mentioned in ./PROBLEMS, case dismissed
> But I cannot find anything related to my situation:
You're got to read between lines. "Explicitly mentioned in ./PROBLEMS"
might as well mean "./PROBLEMS file was just modified to explicitly
mention the problem in question." Also note that your situation is
indirectly covered by SUPPORT section in ./README file:
If you have any problems with OpenSSL then please take the following
- Remove compiler optimisation flags
So that we shouldn't have this discussion at all:-)
> grep -n '^\*' PROBLEMS
> 1:* System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X.
> 42:* Parallell make leads to errors
> 51:* Bugs in gcc 3.0 triggered
If you have to know this paragraph now reads:
* Bugs in gcc triggered
- According to multiple problem reports, some of our message digest
implementations trigger bug[s] in code optimizer in gcc 3.3 for
sparc64 and gcc 2.96 for ppc. Former fails to complete RIPEMD160
test, while latter - SHA one.
The recomendation is to upgrade your compiler. This naturally
applies to other similar cases.