Hi,

> I am getting the following installation error:
> 
>       /tmp/ccqCH1zS.s: Assembler messages:
>       /tmp/ccqCH1zS.s:119: Error: Incorrect register `%rbx' used with `l'
> suffix
>       /tmp/ccqCH1zS.s:131: Error: Incorrect register `%rbx' used with `l'
> suffix
>       make[2]: *** [rand_unix.o] Error 1
>       make[2]: Leaving directory
> `/home/dlecky/perl/lib/openssl-0.9.8/crypto/rand'
>       make[1]: *** [subdirs] Error 1
>       make[1]: Leaving directory
> `/home/dlecky/perl/lib/openssl-0.9.8/crypto'
>       make: *** [build_crypto] Error 1
> 
> Note that I ran config as
>       ./config no-asm
> Then the output of make appeared clean until the last few lines, which are
> those copied above.  
> 
> On make test, a number of tests were skipped or failed.  The attachment  
> <<report.txt>>  report.txt contains the redirect of std output of make
> report,

README is not specific about this, but 'make report' command does print 
"Test report in file testlog" at the end of execution. And the mentioned 
'testlog' file is the one you're expected to provide, as it contains 
additional information which is of interest in such cases, in particular 
compiler version and vague hint about distribution. But enough about sad:-)

The above mentioned error message indicates rather a compiler bug, than 
a problem with OpenSSL code, because source file in question does not 
contain *any* references to our inline assembler code. OpenSSL as whole 
and rand_unix.c in particular is known to be compilable on AMD64 at very 
least by gcc 3.3.4 and 3.4.3. It *might* be misconfigured development 
environment [misplaced .h-files], but in such case it should have failed 
earlier... To resolve problem upgrade your compiler to later version. 
Lowering optimization might help as well... As all of these is beyond 
our control I'm dismissing the case as "not OpenSSL problem." A.

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

Reply via email to