From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake and e2fsprogs-1.41.9?
Date: Mon, 11 Jan 2010 17:19:23 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001111718250.2601@localhost> (raw)
In-Reply-To: <6ec4247d1001111337x5a5572a2l74d23bf1bfa03a68@mail.gmail.com>
On Tue, 12 Jan 2010, Graham Gower wrote:
> Yes, there is a build issue with e2fsprogs 1.41.5. I experienced it
> on a slackware64-13.0 host. It is not a Fedora issue, it is a bug in
> the Makefile. If you look in the Makefile you will see that the
> e2fsck dependency resolves to something containing "-lpthread".
>
> Why this doesn't cause issues for anyone else is beyond me. I can't
> even do a native, out of oe, build of e2fsprogs 1.41.5.
thank you immensely for clarifying that, now i can stop fighting
with it. is someone already working on upgrading e2fsprogs to 1.41.9?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2010-01-11 22:22 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
2010-01-11 21:37 ` Graham Gower
2010-01-11 21:55 ` Philip Balister
2010-01-11 22:19 ` Robert P. J. Day [this message]
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=alpine.LFD.2.00.1001111718250.2601@localhost \
--to=rpjday@crashcourse.ca \
--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