From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12701] New: [patch] wpa_supplicant must depend on openssl
Date: Thu, 26 Mar 2020 19:22:54 +0000 [thread overview]
Message-ID: <bug-12701-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12701
Bug ID: 12701
Summary: [patch] wpa_supplicant must depend on openssl
Product: buildroot
Version: 2020.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: shaforostoff at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
with BR2_PACKAGE_OPENSSH=n building buildroot results in errors:
buildroot/output/host/lib/gcc/arm-buildroot-linux-gnueabihf/8.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld:
../src/eap_peer/eap_teap.o: in function `eap_teap_session_id':
buildroot/build/wpa_supplicant-2.9/wpa_supplicant/../src/eap_peer/eap_teap.c:741:
undefined reference to `tls_get_tls_unique'
buildroot/build/wpa_supplicant-2.9/wpa_supplicant/../src/eap_peer/eap_teap.c:1828:
undefined reference to `tls_connection_get_cipher_suite'
buildroot/output/host/lib/gcc/arm-buildroot-linux-gnueabihf/8.3.0/../../../../arm-buildroot-linux-gnueabihf/bin/ld:
../src/eap_common/eap_teap_common.o: in function `eap_teap_tls_prf':
14:15:20
buildroot/build/wpa_supplicant-2.9/wpa_supplicant/../src/eap_common/eap_teap_common.c:75:
undefined reference to `tls_prf_sha256'
and so on. The fix is to add WPA_SUPPLICANT_DEPENDENCIES=opessl
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-03-26 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 19:22 bugzilla at busybox.net [this message]
2020-03-26 19:43 ` [Buildroot] [Bug 12701] [patch] wpa_supplicant must depend on openssl 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-12701-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.