From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-netifaces: add -x option to fix cross-compilation
Date: Mon, 9 Jan 2012 11:20:18 +0100 [thread overview]
Message-ID: <20120109112018.64832095@skate> (raw)
In-Reply-To: <4F0ABA03.3030206@visionsystems.de>
Le Mon, 09 Jan 2012 10:57:23 +0100,
Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
> That's really strange. I used CodeSourcery toolchain and had no
> problems, but with native BR toolchain I have the same behavior as
> yours. I'll look into this issue.
CodeSourcery toolchains use glibc, so they have IPv6 support enabled.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-09 10:20 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 [this message]
2012-01-09 10:35 ` Peter Korsgaard
2012-01-09 10:40 ` Yegor Yefremov
2012-01-10 12:48 ` Peter Korsgaard
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=20120109112018.64832095@skate \
--to=thomas.petazzoni@free-electrons.com \
--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