From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building wpa_supplicant using external toolchain
Date: Thu, 06 May 2010 12:10:39 -0300 [thread overview]
Message-ID: <4BE2DBEF.8010702@zacarias.com.ar> (raw)
In-Reply-To: <i2i3e7e6aaa1005060454sda263981v97a394b1818a8c85@mail.gmail.com>
On 05/06/2010 08:54 AM, Marc-Andr? H?bert wrote:
> Hello,
>
> I get an error when I try to get to building wpa_supplicant. I
> configured buildroot to use CodeSourcery Lite 2009q1.
>
> I tried both the 2010.02 stable release and the current git source
> tree and obtained the same results.
>
> The error I get is (I truncated the object list):
> /home/vadmin/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-gcc
> -o wpa_supplicant ... ../src/l2_packet/l2_packet_linux.o -lssl
> -lcrypto -ldl
> /home/vadmin/CodeSourcery/Sourcery_G++_Lite/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/../../../../arm-none-linux-gnueabi/bin/ld:
> cannot find -lssl
>
> This fails because there is no libssl.so in the CodeSourcery
> toolchain. But buildroot has built openssl just before so it is
> available somewhere. It builds just fine if I manually instruct
> wpa_supplicant to use the libssl from openssl.
>
> Now if I understand how buildroot does things, I guess it should do
> something like this:
> -Copy libssl.so from openssl to the staging dir
> -Configure wpa_supplicant to use --sysroot with the staging dir
> -Copy the libssl.so to the target root fs
>
> Or am I supposed to patch my external toolchain myself?
> Thank you very much
> Marc
Try this patch to see if it fixes your problem...
Regards.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buildroot-wpa_supplicant-external-toolchain.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100506/bc4cfa5d/attachment.diff>
next prev parent reply other threads:[~2010-05-06 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 11:54 [Buildroot] Problem building wpa_supplicant using external toolchain Marc-André Hébert
2010-05-06 15:10 ` Gustavo Zacarias [this message]
2010-05-06 21:13 ` Peter Korsgaard
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=4BE2DBEF.8010702@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.