From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 497] New: OpenSSL RSA key generation hangs on x86_64
Date: Wed, 29 Jul 2009 14:23:51 +0000 (UTC) [thread overview]
Message-ID: <bug-497-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=497
Target: x86_64
Summary: OpenSSL RSA key generation hangs on x86_64
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: info at je-eigen-domein.nl
CC: buildroot at uclibc.org
Estimated Hours: 0.0
OpenSSL ends up in an endless 100% CPU loop when generating keys on x86_64.
E.g. when running "openssh" for the first time, or executing "openssl genrsa"
It seems that the openssl library buildroot produces includes code for 32-bit
systems, and does not work properly on x86_64.
In openssl.mk It tests for BR2_ARCH:
==
OPENSSL_TARGET_ARCH=generic32
[...]
ifeq ($(BR2_ARCH),x86_64)
OPENSSL_TARGET_ARCH=x86_64
endif
==
Not sure why, but this does not seem to work, and OpenSSL always builds as
"generic32"
If I use $(ARCH) instead, it does work properly and solves the key generation
problem:
==
ifeq ($(ARCH),x86_64)
OPENSSL_TARGET_ARCH=x86_64
endif
==
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-07-29 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 14:23 bugzilla at busybox.net [this message]
2009-07-29 15:07 ` [Buildroot] [Bug 497] OpenSSL RSA key generation hangs on x86_64 bugzilla at busybox.net
2009-07-29 19:15 ` bugzilla at busybox.net
2009-07-29 19:51 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-497-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.