Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-netifaces: add -x option to fix cross-compilation
Date: Mon, 09 Jan 2012 11:40:30 +0100	[thread overview]
Message-ID: <4F0AC41E.6030701@visionsystems.de> (raw)
In-Reply-To: <87y5thduyo.fsf@macbook.be.48ers.dk>

Am 09.01.2012 11:35, schrieb Peter Korsgaard:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> 
>  Thomas> Le Mon, 09 Jan 2012 10:57:23 +0100,
>  Thomas> 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.
> 
>  Thomas> CodeSourcery toolchains use glibc, so they have IPv6 support enabled.
> 
> Yes, but that doesn't explain the 2nd error (missing ;):
> 
>         Py_XDECREF (dict);
>         Py_XDECREF (list)
>         Py_XDECREF (family);
> 

I've activated UCLIBC_SUPPORT_AI_ADDRCONFIG and now I can compile netifaces without a problem with native toolchain. Here is my .config for reference. Also take a look at this thread: http://lists.busybox.net/pipermail/uclibc/2008-August/040778.html

Yegor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config
Type: application/xml
Size: 20230 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120109/d77b9158/attachment-0001.wsdl>

  reply	other threads:[~2012-01-09 10:40 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 [this message]
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=4F0AC41E.6030701@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --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