From: Paul Sokolovsky <pmiscml@gmail.com>
To: Grant Edwards <grante@visi.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: How do you find a rev of OE that will build?
Date: Fri, 21 Dec 2007 02:47:15 +0200 [thread overview]
Message-ID: <1344229699.20071221024715@gmail.com> (raw)
In-Reply-To: <fkerm2$nnf$1@ger.gmane.org>
Hello Grant,
Friday, December 21, 2007, 12:51:46 AM, you wrote:
> On 2007-12-19, Grant Edwards <grante@visi.com> wrote:
>> I've been following the GettingStarted page trying to build
>> task-bask for about a week now, and I always hit errors due to
>> failed patches. Here's the error du jour after doing a
>> pull/update about a half hour ago:
>>
>> [...]
>> NOTE: Running task 284 of 976 (ID: 650, /home/grante/quarq/oe/org.openembedded.dev/packages/python/python-native_2.5.1.bb, do_patch)
>> NOTE: package python-native-2.5.1: started
>> NOTE: package python-native-2.5.1-ml1: task do_patch: started
>> NOTE: Applying patch 'bindir-libdir.patch'
>> ERROR: Error in executing:
>> ERROR: Exception:__builtin__.CmdError Message:Command Error: exit status: 1 Output:
>> Applying patch bindir-libdir.patch
>> patching file Makefile.pre.in
>> Hunk #1 FAILED at 78.
>> 1 out of 1 hunk FAILED -- rejects in file Makefile.pre.in
> [...]
> I updated today and tried again. No joy. python-native_2.5.1
> still fails when applying patches with the same error.
> Is there a way to tell bitbake to use an older version of the
> package -- presuming there are older versions that will build?
> Are packages in the .dev branch normally unbuildable for
> extended periods of time? Should I not be trying to build
> using the .dev branch?
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? ;-) And the best place to continue this is the bugtracker.
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-21 0:47 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 [this message]
2007-12-21 2:40 ` Grant Edwards
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=1344229699.20071221024715@gmail.com \
--to=pmiscml@gmail.com \
--cc=grante@visi.com \
--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.