From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Juergen Gross' <jgross@suse.com>,
'Stefano Stabellini' <sstabellini@kernel.org>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH RESEND] xen: limit pkg-config to PKG_CONFIG_PATH for xen libraries
Date: Mon, 27 Mar 2017 08:01:07 +0000 [thread overview]
Message-ID: <feef084fd323400187f420a2f0588597@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <f18632d1-dba1-084d-893c-aca6176754b6@suse.com>
> -----Original Message-----
[snip]
>
> To sum it up we have to care about the following scenarios:
>
> a) Xen in-tree build, Xen >= 4.9
> b) Xen in-tree build, Xen < 4.9
> c) build out-of-Xen-tree
>
> combined with any of:
>
> 1) no Xen installed on build machine
> 2) Xen >= 4.9 installed
> 3) Xen < 4.9 installed
>
> 1) + c) is not supported, all other combinations should work.
>
Good summary.
> I suggest the following modifications of my patch:
>
> - keep the test program for detection of Xen 4.9
> - scan the extra ldflags for special mentioning of tools/libxc
> to detect Xen in-tree build < 4.9 (will detect 4.9, too, but
> this is no problem), set xen_in_tree_old if found
> - if xen_in_tree_old found, don't use pkg-config for Xen version
> detection and flags
> - otherwise try pkg-config first
>
> This should cover all cases we need.
>
That sounds plausible.
Thanks,
Paul
>
> Juergen
prev parent reply other threads:[~2017-03-27 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 17:20 [Qemu-devel] [PATCH RESEND] xen: limit pkg-config to PKG_CONFIG_PATH for xen libraries Paul Durrant
2017-03-24 18:44 ` Juergen Gross
2017-03-24 19:11 ` Stefano Stabellini
2017-03-24 19:17 ` Paul Durrant
2017-03-24 19:34 ` Paul Durrant
2017-03-27 5:45 ` Juergen Gross
2017-03-27 8:01 ` Paul Durrant [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=feef084fd323400187f420a2f0588597@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=jgross@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).