From: Matthew Fernandez <matthew.fernandez@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Missing dependency checks in qemu build
Date: Sat, 22 Mar 2014 11:10:56 +1100 [thread overview]
Message-ID: <532CD510.60407@gmail.com> (raw)
Hi all,
This only came to my attention when building qemu on a colleague's machine recently, but there are
some dependencies for the build that are not detected during the standard `configure` process. In
particular, missing autoconf was not detected until running `make` itself. Also missing libtool
produced a fairly obtuse error. It was reasonably apparent to me what went wrong, but thoroughly
confusing to my colleague.
Should the configure process be made more bulletproof? Perhaps assuming the existence of these
things seems fine to others. I don't know what the status quo is here. By the way, this is with
reference to the qemu 1.7.0 release. I'm not on the list currently, so please CC me when replying.
Thanks,
Matt
next reply other threads:[~2014-03-22 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 0:10 Matthew Fernandez [this message]
2014-03-22 7:23 ` [Qemu-devel] Missing dependency checks in qemu build Stefan Weil
2014-03-23 0:03 ` Matthew Fernandez
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=532CD510.60407@gmail.com \
--to=matthew.fernandez@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).