From: Steffen Sledz <sledz@dresearch-fe.de>
To: Tom Rini <tom.rini@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [2011.03-maintenance 3/3] python-2.6.6: Fix python-2.6.6 build failure on linux-3.x
Date: Tue, 27 Mar 2012 15:06:49 +0200 [thread overview]
Message-ID: <4F71BB69.5010202@dresearch-fe.de> (raw)
In-Reply-To: <4F71B9A5.3080405@opendreambox.org>
On 27.03.2012 14:59, Andreas Oberritter wrote:
> On 27.03.2012 14:51, Steffen Sledz wrote:
>> On 27.03.2012 14:44, Andreas Oberritter wrote:
>>> On 27.03.2012 14:07, Steffen Sledz wrote:
>>>> From: Ulf Samuelsson <ulf_samuelsson@telia.com>
>>>>
>>>> python-2.6.6 build will crash when host is running linux kernel 3.x.
>>>>
>>>> Fix backported from openembedded-core.
>>>> meta/recipes-devtools/python/python/07-linux3-regen-fix.patch
>>>
>>> This patch has been superseded by a backport from upstream python,
>>> causing linux2 to be used for all kernel versions. See commit
>>> accb2b728ab10cae20be59253a56ac6410b8de10 in oe-core.
>>
>> Is this patch available in oe-classic master?
>
> I don't know.
>
>> I'm just trying to keep the 2011.03-maintenance branch usable with a minimum of work. And the one from the pull request is good enough for me at the moment.
>
> I don't want to block your pull request. I was just trying to make you
> aware of problems that have already been fixed in oe-core. Building
> python on 32-bit vs. 64-bit build systems and on 2.x vs. 3.x kernels
> (running on the build system) produces different results, even with this
> patch applied. Some of these problems have already been fixed in
> oe-core, some are still pending (patches were sent to the oe-core
> mailing list).
Tom, would be nice, if you accept my pull request for the moment.
*If* i have some time later i can try to have a look at oe-core stuff. Or may be someone else.
Thx,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2012-03-27 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 12:06 [2011.03-maintenance 0/3] pull request 20120327 Steffen Sledz
2012-03-27 12:07 ` [2011.03-maintenance 1/3] python-scons_1.3.0: add `python-native` to `DEPENDS_virtclass-native` Steffen Sledz
2012-03-27 12:07 ` [2011.03-maintenance 2/3] python-2.6.6: backport pkgconfig support from version 2.7.1 and bump PR Steffen Sledz
2012-03-27 12:07 ` [2011.03-maintenance 3/3] python-2.6.6: Fix python-2.6.6 build failure on linux-3.x Steffen Sledz
2012-03-27 12:44 ` Andreas Oberritter
2012-03-27 12:51 ` Steffen Sledz
2012-03-27 12:59 ` Andreas Oberritter
2012-03-27 13:06 ` Steffen Sledz [this message]
2012-03-29 17:12 ` [2011.03-maintenance 0/3] pull request 20120327 Tom Rini
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=4F71BB69.5010202@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tom.rini@gmail.com \
/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.