From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3445] New: Not working openssl-10.0.0d on 386sx
Date: Wed, 9 Mar 2011 10:27:03 +0000 (UTC) [thread overview]
Message-ID: <bug-3445-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3445
Summary: Not working openssl-10.0.0d on 386sx
Product: buildroot
Version: 2011.02
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: milospokorny at seznam.cz
CC: buildroot at uclibc.org
Estimated Hours: 0.0
In buildroot configuration, selecting 'Target architecture variant' i386 and
then running on 80386sx processor makes libcrypto generate SIGILL (running ssh,
openvpn etc ). For this configuration, parametter "386" should be passed to
configure script of openssl.
--
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:[~2011-03-09 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 10:27 bugzilla at busybox.net [this message]
2011-03-14 17:36 ` [Buildroot] [Bug 3445] Not working openssl-10.0.0d on 386sx bugzilla at busybox.net
2011-04-01 19:57 ` 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-3445-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox