From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake and e2fsprogs-1.41.9?
Date: Mon, 11 Jan 2010 09:17:37 -0500 [thread overview]
Message-ID: <4B4B3301.2090808@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1001110856460.28813@localhost>
On 01/11/2010 09:05 AM, Robert P. J. Day wrote:
> On Mon, 11 Jan 2010, Philip Balister wrote:
>
>> On 01/11/2010 07:27 AM, Robert P. J. Day wrote:
>>>
>>> apologies as i accidentally deleted the emails i was going to
>>> respond to, the thread is here:
>>>
>>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-January/016074.html
>>>
>>> and here:
>>>
>>> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-January/016097.html
>>>
>>> graham gower suggests that an upgrade to e2fsprogs might be the
>>> solution. i might have time later this week to try that upgrade
>>> unless someone else gets to it first and checks it in to the dev
>>> branch.
>>>
>>> what would be useful, though, is to get some confirmation that there
>>> really *was* a build error in the current version. otherwise, i'll be
>>> back where i started.
>>
>> It builds on my F11 machine.
>
> which version of e2fsprogs are you referring to? the current 1.41.5
> version, or the newer one? i know i'm sounding tedious, but it's been
> literally *weeks* since i've been able to build e2fsprogs on my F12
> system from the OE dev checkout, and it's the exact same error every
> single time and i am fresh out of ideas.
The current 1.41.5.
Philip
>
> ERROR: function do_compile failed
> ERROR: see log in
> /home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/temp/log.do_compile.3121
> NOTE: Task failed:
> /home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/temp/log.do_compile.3121
> ERROR: TaskFailed event exception, aborting
> ERROR: Build of
> /home/rpjday/oe/openembedded/recipes/e2fsprogs/e2fsprogs_1.41.5.bb
> do_compile failed
> ERROR: Task 8
> (/home/rpjday/oe/openembedded/recipes/e2fsprogs/e2fsprogs_1.41.5.bb,
> do_compile) failed
> ...
> make[2]: Entering directory
> `/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/e2fsprogs-1.41.5/e2fsck'
> COMPILE_ET prof_err.et
> CC gen_crc32table
> GEN32TABLE crc32table.h
> CC crc32.c
> CC dict.c
> CC unix.c
> CC e2fsck.c
> CC super.c
> CC pass1.c
> CC pass1b.c
> CC pass2.c
> CC pass3.c
> CC pass4.c
> CC pass5.c
> CC journal.c
> CC badblocks.c
> CC util.c
> CC dirinfo.c
> CC dx_dirinfo.c
> CC ehandler.c
> CC problem.c
> CC message.c
> CC recovery.c
> CC region.c
> CC revoke.c
> CC ea_refcount.c
> CC rehash.c
> CC profile.c
> CC prof_err.c
> make[2]: *** No rule to make target `-lpthread', needed by `e2fsck'.
> Stop.
>
> is this the error that upgrading to 1.41.9 is supposed to fix?
> clearly, this is some sort of build error where a build *flag* is
> being misinterpreted as a make *target*.
>
> rday
> --
>
>
> ========================================================================
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> ========================================================================
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-01-11 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 12:27 bitbake and e2fsprogs-1.41.9? Robert P. J. Day
2010-01-11 13:43 ` Philip Balister
2010-01-11 14:05 ` Robert P. J. Day
2010-01-11 14:17 ` Philip Balister [this message]
2010-01-11 21:37 ` Graham Gower
2010-01-11 21:55 ` Philip Balister
2010-01-11 22:19 ` Robert P. J. Day
2010-01-11 22:39 ` Graham Gower
2010-01-11 23:14 ` Robert P. J. Day
2010-01-12 0:07 ` [PATCH] Add e2fsprogs 1.41.9. [WAS Re: bitbake and e2fsprogs-1.41.9?] Graham Gower
[not found] ` <alpine.LFD.2.00.1001121117040.24279@localhost>
2010-01-12 16:27 ` Robert P. J. Day
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=4B4B3301.2090808@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox