xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH] build: add --with-rundir option to configure
Date: Wed, 22 Feb 2017 07:55:02 +0000	[thread overview]
Message-ID: <c121d5ec-ac0e-d299-5d7c-e8ca2bbbbaf6@citrix.com> (raw)
In-Reply-To: <96342cbd-ba1c-bb06-229a-5e03000571e3@suse.com>

On 22/02/17 07:53, Juergen Gross wrote:
> On 20/02/17 16:19, Andrew Cooper wrote:
>> On 20/02/17 14:43, Juergen Gross wrote:
>>> On 20/02/17 15:31, Wei Liu wrote:
>>>> On Thu, Feb 16, 2017 at 08:47:07AM +0100, Juergen Gross wrote:
>>>>> There have been reports that Fedora 25 uses /run instead of /var/run.
>>>>>
>>>>> Add a --with-rundir option ito configure to be able to specify that
>>>> I've read this thread but I'm not sure if I need to take any action or
>>>> all the comments addressed -- especially the part about autoconf.
>>> Andrew, are you fine with my answer regarding autoconf? Or do you have
>>> some information regarding --runstatedir which could help?
>> Oh sorry.  Didn't realise I was blocking here.  I have no specific
>> information, other than the quick search I did.
>>
>> Can't the future problem be worked around just with if autoconf version
>> < 2.70 ?
> I don't think it is possible to add configure options other than
> --disable-*, --enable-*, --with-* or --without-* by other means than
> patching general.m4 of autoconf. I don't think we want to do that.

Ok.  In which case lets go with 3).

~Andrew

>
> So the possibilities are:
>
> 1. don't support /run instead of /var/run via configure
> 2. patch autoconf to support --runstatedir
> 3. take this patch adding support via --with-rundir and possibly
>    switch over to --runstatedir when a new autoconf version is
>    available
>
> I'm in favor of (3.).
>
>
> Juergen
>


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

  reply	other threads:[~2017-02-22  7:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  7:47 [PATCH] build: add --with-rundir option to configure Juergen Gross
2017-02-16 13:52 ` Boris Ostrovsky
2017-02-16 14:12   ` Andrew Cooper
2017-02-16 14:34     ` Juergen Gross
2017-02-16 14:15   ` Juergen Gross
2017-02-17 16:41   ` Konrad Rzeszutek Wilk
2017-02-17 17:27     ` Boris Ostrovsky
2017-02-20 14:31 ` Wei Liu
2017-02-20 14:43   ` Juergen Gross
2017-02-20 15:19     ` Andrew Cooper
2017-02-22  7:53       ` Juergen Gross
2017-02-22  7:55         ` Andrew Cooper [this message]
2017-02-22 11:37         ` Wei Liu
2017-02-24 16:01           ` Doug Goldstein
2017-02-24 16:06         ` Doug Goldstein
2017-02-24 16:14           ` Juergen Gross
2017-02-24 16:49             ` Doug Goldstein
2017-02-24 17:13               ` Juergen Gross
2017-02-23 11:41 ` Wei Liu

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=c121d5ec-ac0e-d299-5d7c-e8ca2bbbbaf6@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --cc=wei.liu2@citrix.com \
    --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).