From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: tcpdump: bitbake throws autoconf errors, error message confusing
Date: Fri, 04 Jul 2014 10:42:22 +0100 [thread overview]
Message-ID: <53B676FE.50809@communistcode.co.uk> (raw)
So tcpdump is failing to build in my latest uprev to all things HEAD.
The error message is a touch cryptic:
ERROR: This autoconf log indicates errors, it looked at host include
and/or library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/home/jack/Work/oe-core.git/test-build/tmp-eglibc/work/core2-32-oe-linux/tcpdump/4.5.1-r0/build'
ERROR: Function failed: do_qa_configure
log: http://ix.io/dg9
Looking at the log I can't see where that specific path is used... can
anyone shed any light?
Cheers,
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
Cambridgeshire, UK
http://www.embed.me.uk
--
next reply other threads:[~2014-07-04 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 9:42 Jack Mitchell [this message]
2014-07-04 10:14 ` tcpdump: bitbake throws autoconf errors, error message confusing Robert Yang
2014-07-04 10:31 ` Jack Mitchell
2014-07-04 12:08 ` Andrea Adami
2014-07-04 12:09 ` Jack Mitchell
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=53B676FE.50809@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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