From: Grant Edwards <grante@visi.com>
To: openembedded-devel@openembedded.org
Subject: Re: How do you find a rev of OE that will build?
Date: Fri, 21 Dec 2007 02:40:48 +0000 (UTC) [thread overview]
Message-ID: <fkf93g$pe8$1@ger.gmane.org> (raw)
In-Reply-To: 1344229699.20071221024715@gmail.com
On 2007-12-21, Paul Sokolovsky <pmiscml@gmail.com> wrote:
> No, anything on critical path to build a common embedded system
> image can't be broken and unnoticed for long. I rebuilt python-native
> for you:
>
> NOTE: package python-native-2.5.1-ml1: task do_patch: started
> NOTE: Applying patch 'bindir-libdir.patch'
> NOTE: Applying patch 'cross-distutils.patch'
> NOTE: Applying patch 'dont-modify-shebang-line.patch'
> NOTE: Applying patch 'default-is-optimized.patch'
> NOTE: package python-native-2.5.1-ml1: task do_patch: completed
>
> Anyway, as you see, it's not some dark magic failing, but
> merely a patch application. So, why don't you look closer and
> see what corrupts the data - your tar, a quilt built on your
> system, or your kernel? ;-)
OK. It just seems odd that 100+ other packages would build
fine, but when one particular package fails it's not the
package that's suspect but the tools that work fine for 100+
other OE packages and and entire Gentoo system build.
> And the best place to continue this is the bugtracker.
Thanks.
--
Grant Edwards grante Yow! Why is it that when
at you DIE, you can't take
visi.com your HOME ENTERTAINMENT
CENTER with you??
prev parent reply other threads:[~2007-12-21 2:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 2:02 How do you find a rev of OE that will build? Grant Edwards
2007-12-20 22:51 ` Grant Edwards
2007-12-21 0:47 ` Paul Sokolovsky
2007-12-21 2:40 ` Grant Edwards [this message]
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='fkf93g$pe8$1@ger.gmane.org' \
--to=grante@visi.com \
--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.