From: Vitus Jensen <vjensen@gmx.de>
To: openembedded-devel@openembedded.org
Subject: Re: python roadmap
Date: Tue, 17 Feb 2009 22:36:50 +0000 (UTC) [thread overview]
Message-ID: <gnfe62$7mo$1@ger.gmane.org> (raw)
In-Reply-To: gne20v$aj$1@ger.gmane.org
Am Tue, 17 Feb 2009 10:03:12 +0000 schrieb Vitus Jensen:
> Am Tue, 17 Feb 2009 09:09:43 +0100 schrieb Koen Kooi:
>
>> On 17-02-09 07:35, Vitus Jensen wrote:
>>> Am Thu, 05 Feb 2009 08:35:31 +0000 schrieb Vitus Jensen:
>>>
>>>> Am Wed, 14 Jan 2009 15:47:26 +0100 schrieb Michael 'Mickey' Lauer:
>>>>
>>>>> Thanks to some extrashifts this work has proceeded faster than
>>>>> scheduled. I plan to merge mickey/python26 into master on friday. If
>>>>> you see something dangerous, yell.
>>>> Yell ;-)
>>>>
>>>> See http://bugs.openembedded.net/show_bug.cgi?id=5013
>>>>
>>>> python26 fails to build for the big-endian machines I tried, namely
>>>> nslu2be. And as python25 was removed it is a real blocker for
>>>> packages which DEPEND on pathon, which inturn is the case for php.
>>>> And php I'm trying to get a version working again.
>>> ...
>>>
>>> Does anyone build packages for bigendian machines?
>>
>> yes
>
> OK. Restarting from scratch...
... doesn't build after clearing TMPDIR.
I will reinstall my slug to nslu2le and build those packages.
--
Vitus Jensen, Hannover, Germany, Earth, Milky Way, Universe (current)
next prev parent reply other threads:[~2009-02-17 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 23:19 python roadmap Michael 'Mickey' Lauer
2009-01-14 14:47 ` Michael 'Mickey' Lauer
2009-02-05 8:35 ` Vitus Jensen
2009-02-17 6:35 ` Vitus Jensen
2009-02-17 8:09 ` Koen Kooi
2009-02-17 10:03 ` Vitus Jensen
2009-02-17 22:36 ` Vitus Jensen [this message]
2009-02-26 1:15 ` Vitus Jensen
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='gnfe62$7mo$1@ger.gmane.org' \
--to=vjensen@gmx.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.