From: Ian Campbell <Ian.Campbell@citrix.com>
To: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>
Cc: "Roger Pau Monné" <roger.pau@entel.upc.edu>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: autoconf/ debian 6.0 - missing dependency checks
Date: Fri, 2 Mar 2012 08:51:12 +0000 [thread overview]
Message-ID: <1330678272.18632.41.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <CAP8mzPNupc1tNxXstxAbRUzzXLbeMMi+ArUwFPa6XBKR74G8Kg@mail.gmail.com>
On Thu, 2012-03-01 at 19:22 +0000, Shriram Rajagopalan wrote:
> I just did a ./configure and then make on a fresh debian 6.0 64-bit
> install.
> ./configure caught most of the missing dependencies except the
> following,
> which caused compilation failures.
>
> 1. libncurses5-dev (I get errors from tools/misc, concerning
> gtraceview)
Also used by xentop so I think we should make this a hard dependency
check. If it were just gtraceview a soft dependency would have been ok.
> 2. bin86 & bcc & iasl - during firmware compilation
The first two are used for vgabios and rombios only, I think.
We should eventually have --{enable,disable}-rombios but for now this is
also a hard dependency.
iasl is used by tools/firmware/hvmloader/... that's a hard dependency.
> 3. python-dev (from tools/python/xen/lowlevel/xc)
We should eventually have --enable-python/--enable-xend etc but for now
this is a hard dependency.
> I am not sure if I was doing something wrong or if its the configure
> script missing these dependency checks.
Missing I think. CCing Roger.
>
>
> shriram
prev parent reply other threads:[~2012-03-02 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 19:22 autoconf/ debian 6.0 - missing dependency checks Shriram Rajagopalan
2012-03-02 8:51 ` Ian Campbell [this message]
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=1330678272.18632.41.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=roger.pau@entel.upc.edu \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xen.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).