Hello,

This sound great :)

SIGILL is raised when the program try to execute an assembly code that the CPU 
cannot execute. It mean that the library or the binary is miscompiled.

Regards,

On Tuesday 01 March 2011 20:20:58 Marius Strobl wrote:
> On Tue, Mar 01, 2011 at 10:31:16AM +0100, Alexandre Martins wrote:
> > Dear,
> > 
> > Have you extracted the tarball fo openssl source (1.0.0d) in
> > crypto/openssl ?
> 
> Ah, I missed that, the last couple of mails in this thread were only
> talking about the patch :)
> With the tarball untared it actually builds and works on sparc64 as
> far as ssh(d) and HTTPS via fetch are concerned. The problem reports
> (programs getting killed with SIGILL probably due to an infinite
> recursion or some such) were about apache and unbound using an
> OpenSSL 1.0.0 port. I'm not sure whether their use of OpenSSL would
> make a difference or the port is broken.
> 
> Marius
-- 
Alexandre Martins
NETASQ

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to