From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] python.inc: add `--disable-ipv6` to `EXTRA_OECONF`
Date: Fri, 14 Jan 2011 22:44:52 +0100 [thread overview]
Message-ID: <igqg4k$lv7$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTineRKBLdhFHm-p2K1qK49vXe0tp6N1c3XeSUVbS@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14-01-11 21:16, Khem Raj wrote:
> On Fri, Jan 14, 2011 at 11:20 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> On 14-01-11 19:58, Koen Kooi wrote:
>>>> On 14-01-11 10:10, Paul Menzel wrote:
>>>>> From b2e249702a0f6b5e36a4b095f5a4c495aa5ec14f Mon Sep 17 00:00:00 2001
>>>>> From: Paul Menzel <paulepanter@users.sourceforge.net>
>>>>> Date: Fri, 14 Jan 2011 09:48:08 +0100
>>>>> Subject: [PATCH] python.inc: add `--disable-ipv6` to `EXTRA_OECONF`
>>>>
>>>>> Since commit d729d14d [1] task `configure` for `python_2.6.5` and `python_2.7.1` fails with the following error message when compiling with `angstrom_2008.1` for `MACHINE = "beagleboard"`.
>>>>
>>>>> checking for major... yes
>>>>> checking for getaddrinfo... yes
>>>>> checking getaddrinfo bug... buggy
>>>>> Fatal: You must get working getaddrinfo() function.
>>>>> or you can specify "--disable-ipv6".
>>>>> ERROR: Function do_configure failed
>>>>
>>>>> Disable IPv6 for now in Python unconditionally until a better solution is found.
>>>>
>>>> I don't think disabling ipv6 is the way to go, I'm comparing the eglibc
>>>> before and after d729d14d to see if that reveals a clue. If it doesn't,
>>>> let's put in your patch for the time being.
>
> .... and the difference is that options-group.config is empty before d72
> and fully populated after it. OPTION_EGLIBC_ADVANCED_INET6 is set to Y
> in both cases it seems.
>
>> I was expecting it to converge to this. Do u see that libraries
>> libc.so before and after have different content too ?
>> Could be that the option config mechanism is getting it wrong somehow
>> may be I should only populate options-group.config
>> with disabled features
Populating it only with disabled features would match the old behaviour
and should make python build again. I doesn't give us the root cause,
but at least it would build :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNMMPUMkyGM64RGpERAr0QAKCg3AB+AqMcNQM8svqVbvnIpD6WLwCgri+J
2dimtKfPQ/BC9sqTzfURWrA=
=qmN5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-01-14 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:10 [PATCH] python.inc: add `--disable-ipv6` to `EXTRA_OECONF` Paul Menzel
2011-01-14 18:58 ` Koen Kooi
2011-01-14 19:20 ` Koen Kooi
2011-01-14 20:16 ` Khem Raj
2011-01-14 21:44 ` Koen Kooi [this message]
2011-01-14 22:12 ` Khem Raj
2011-01-15 22:51 ` Khem Raj
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='igqg4k$lv7$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/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.