From: Olaf Hering <olaf@aepfle.de>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: configure failure
Date: Thu, 23 Feb 2012 14:13:20 +0100 [thread overview]
Message-ID: <20120223131320.GA12900@aepfle.de> (raw)
In-Reply-To: <CAPLaKK474jUie5oN_=qwrs5RDZTcTcu7z5dJ=HegjP4G1fscUw@mail.gmail.com>
On Thu, Feb 23, Roger Pau Monné wrote:
> 2012/2/22 Christoph Egger <Christoph.Egger@amd.com>:
> > On 02/22/12 10:59, Roger Pau Monné wrote:
> >>
> >> 2012/2/22 Christoph Egger<Christoph.Egger@amd.com>:
> >>>
> >>>
> >>> Hi,
> >>>
> >>> configure fails on NetBSD that there is no brctl.
> >>> NetBSD has no brctl, NetBSD has brconfig.
> >>
> >>
> >> Sorry Christoph, the brctl test is going away (from configure at least).
> >
> >
> > There are some more Linux specific tests:
> > - ip
> > - uuid_clear in libuuid
>
> I'm going to fix this right now. Should I commit the output from
> autoconf also with my patches Ian? I'm asking this because we use
> different versions and the output is slightly different.
I also think configure should just check compile time requirements.
ip(1) is most likely not needed to compile and link xen+tools.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-02-23 13:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 9:57 configure failure Christoph Egger
2012-02-22 9:59 ` Roger Pau Monné
2012-02-22 10:21 ` Christoph Egger
2012-02-22 10:30 ` Roger Pau Monné
2012-02-22 10:51 ` Christoph Egger
2012-02-22 11:19 ` Roger Pau Monné
2012-02-23 9:18 ` Roger Pau Monné
2012-02-23 13:13 ` Olaf Hering [this message]
2012-02-29 14:46 ` Ian Jackson
2012-02-29 14:46 ` Ian Jackson
2012-02-29 14:53 ` Roger Pau Monné
-- strict thread matches above, loose matches on Subject: below --
2006-11-02 7:24 Brandon Sho
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=20120223131320.GA12900@aepfle.de \
--to=olaf@aepfle.de \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=roger.pau@entel.upc.edu \
--cc=xen-devel@lists.xensource.com \
/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.