From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: bitbake and e2fsprogs-1.41.9?
Date: Mon, 11 Jan 2010 07:27:03 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001110722550.22930@localhost> (raw)
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.
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 reply other threads:[~2010-01-11 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 12:27 Robert P. J. Day [this message]
2010-01-11 13:43 ` bitbake and e2fsprogs-1.41.9? 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
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.1001110722550.22930@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 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.