From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6770] New: openssl bump
Date: Wed, 8 Jan 2014 14:20:57 +0000 (UTC) [thread overview]
Message-ID: <bug-6770-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6770
Summary: openssl bump
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mlweber1 at rockwellcollins.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Noticed a couple packages failing after the openssl bump
(http://git.buildroot.net/buildroot/commit/?id=757690a262fa050ee18847ecee02672f16383b49)
netsnmp (arm build)
....
"checking for authentication support... configure: error: Asked to use OpenSSL
but I couldn't find it."
...
wpa_supplicant (ppc build)
....
LD wpa_cli
CC ../src/crypto/crypto_openssl.c
/accts/mlweber1/proj/br-continuous/cfgs/30-fis-x86-glibc-ext/host/usr/i686-buildroot-linux-gnu/sysroot/usr/lib/libcrypto.a(dso_dlfcn.o):
In function `dlfcn_globallookup':
dso_dlfcn.c:(.text+0x21): undefined reference to `dlopen'
dso_dlfcn.c:(.text+0x37): undefined reference to `dlsym'
...
I've attached configs to reproduce and error logs. I won't get a chance to
investigate these for ~week, but should have some time to test if someone beats
me to a fix :-)
--
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:[~2014-01-08 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:20 bugzilla at busybox.net [this message]
2014-01-08 14:21 ` [Buildroot] [Bug 6770] openssl bump bugzilla at busybox.net
2014-01-08 16:47 ` bugzilla at busybox.net
2014-01-09 3:51 ` bugzilla at busybox.net
2014-01-09 13:35 ` bugzilla at busybox.net
2014-01-09 22:59 ` [Buildroot] [Bug 6770] openssl 1.0.1f fails with ccache bugzilla at busybox.net
2014-01-09 23:21 ` bugzilla at busybox.net
2014-02-07 8:39 ` 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-6770-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