From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] wpa_supplicant doesn't compile
Date: Mon, 09 Dec 2013 11:40:16 +0100 [thread overview]
Message-ID: <87zjoa71f3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CALADVSOXZK_dqB_UGSWKVM8D=E4S8+KkG2Pu6h5EH3d93OOyug@mail.gmail.com> (Javier Alejandro Saenz Leguizamon's message of "Mon, 9 Dec 2013 05:34:17 -0500")
>>>>> "Javier" == Javier Alejandro Saenz Leguizamon <jasaenzl@unal.edu.co> writes:
> Hi, and thx for the quick answer, its probably the toolchain, im
> using codesourcery 2008q3, I'm going to try again with codesoucery
> 2013.11 i also have another problem with openvpn and LZO compression
> but I'm going to fix this
Yes, a toolchain from 2008 can hardly contain uptodate Linux kernel
headers (2.6.29 is from 2009).
In general, you are likely to end up with problems if you try to combine
components of significant different age.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-12-09 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 23:39 [Buildroot] wpa_supplicant doesn't compile Javier Alejandro Saenz Leguizamon
2013-12-09 8:19 ` Peter Korsgaard
2013-12-09 10:34 ` Javier Alejandro Saenz Leguizamon
2013-12-09 10:40 ` Peter Korsgaard [this message]
2013-12-09 18:45 ` Javier Alejandro Saenz Leguizamon
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=87zjoa71f3.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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