From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-netifaces: add -x option to fix cross-compilation
Date: Tue, 10 Jan 2012 13:48:52 +0100 [thread overview]
Message-ID: <87y5tfd8p7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4F0AC41E.6030701@visionsystems.de> (Yegor Yefremov's message of "Mon, 09 Jan 2012 11:40:30 +0100")
>>>>> "Yegor" == Yegor Yefremov <yegor_sub1@visionsystems.de> writes:
Yegor> I've activated UCLIBC_SUPPORT_AI_ADDRCONFIG and now I can
Yegor> compile netifaces without a problem with native toolchain. Here
Yegor> is my .config for reference. Also take a look at this thread:
Yegor> http://lists.busybox.net/pipermail/uclibc/2008-August/040778.html
Thanks. I added (and sent upstream) a patch to get netifaces to build
without ADDRCONFIG.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-01-10 12:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 7:42 [Buildroot] [PATCH] python-netifaces: add -x option to fix cross-compilation yegorslists at googlemail.com
2012-01-09 8:18 ` Peter Korsgaard
2012-01-09 9:57 ` Yegor Yefremov
2012-01-09 10:20 ` Thomas Petazzoni
2012-01-09 10:35 ` Peter Korsgaard
2012-01-09 10:40 ` Yegor Yefremov
2012-01-10 12:48 ` Peter Korsgaard [this message]
2012-01-10 12:47 ` 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=87y5tfd8p7.fsf@macbook.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