From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: any thoughts on current dev branch e2fsprogs build error?
Date: Thu, 3 Dec 2009 04:42:04 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912030424330.12259@localhost> (raw)
on a fully updated dev branch, the tail end of the log file:
... snip ...
making all in e2fsck
make[2]: Entering directory
`/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/e2fsprogs-1.41.5/e2fsck'
CC crc32.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
make[2]: *** No rule to make target `-lpthread', needed by `e2fsck'.
Stop.
make[2]: Leaving directory
`/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/e2fsprogs-1.41.5/e2fsck'
make[1]: *** [all-progs-recursive] Error 1
make[1]: Leaving directory
`/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/e2fsprogs-1.41.5-r1/e2fsprogs-1.41.5'
make: *** [all] Error 2
FATAL: oe_runmake failed
i can provide more details if necessary.
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:[~2009-12-03 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 9:42 Robert P. J. Day [this message]
2009-12-03 9:51 ` any thoughts on current dev branch e2fsprogs build error? Holger Hans Peter Freyther
2009-12-03 17:34 ` 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.0912030424330.12259@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