xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@entel.upc.edu>
To: Jan Beulich <JBeulich@suse.com>
Cc: ian.jackson@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] autoconf: add missing compression checks for libxc
Date: Tue, 6 Mar 2012 18:27:10 +0100	[thread overview]
Message-ID: <CAPLaKK4TcwVWv5pDD=QdoPpBUYifaebvqYwii5tqOiznY0eQqA@mail.gmail.com> (raw)
In-Reply-To: <4F5636750200007800076AF7@nat28.tlf.novell.com>

2012/3/6 Jan Beulich <JBeulich@suse.com>:
>>>> On 06.03.12 at 16:01, Roger Pau Monné<roger.pau@entel.upc.edu> wrote:
>> 2012/3/6 Jan Beulich <JBeulich@suse.com>:
>>> ... are you certain that checking for these symbols in the respective
>>> libraries suffices? The old check really was verifying corresponding
>>> header files' presence.
>>
>> I think it's best to do it this way, what this tests do is try to
>> compile a sample program that uses the library, which is much more
>> closer to the reality than just checking for a header existence. In a
>> strange case you might have the header files, but maybe the library is
>> broken, so we can not use it. What I can do if you want is check for
>> the header files also, something like this?
>
> Hmm, no - I was rather thinking of a real usability test (which implies
> existence), i.e. include the header in the test source snippet. This is
> what really matches reality.

The last patch does this more or less, it's just that not on the same
test. If headers are found and are usable then we perform a library
check, basically it does the same as the previous test found in
tools/libxc/Makefile but also checks that the library is usable for
linking.

> Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-03-06 17:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 19:45 [PATCH] autoconf: add missing compression checks for libxc Roger Pau Monne
2012-03-06 14:30 ` Jan Beulich
2012-03-06 15:01   ` Roger Pau Monné
2012-03-06 15:08     ` Jan Beulich
2012-03-06 17:27       ` Roger Pau Monné [this message]
2012-03-07  7:49         ` Jan Beulich
2012-03-07  9:02           ` Roger Pau Monné
2012-03-07  9:26             ` Jan Beulich
2012-03-13 17:04               ` Ian Jackson
2012-03-14  7:30                 ` Jan Beulich
2012-03-12 11:17     ` Ian Jackson
2012-03-14 11:12     ` Ian Jackson
2012-03-14 13:45       ` Roger Pau Monné
2012-03-14 14:13         ` Ian Jackson
2012-03-14 14:15           ` Roger Pau Monné

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='CAPLaKK4TcwVWv5pDD=QdoPpBUYifaebvqYwii5tqOiznY0eQqA@mail.gmail.com' \
    --to=roger.pau@entel.upc.edu \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@citrix.com \
    --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).