From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH] build: add --with-rundir option to configure
Date: Thu, 16 Feb 2017 14:12:09 +0000 [thread overview]
Message-ID: <358f3ed4-1e65-4023-eb32-eb383694e9e0@citrix.com> (raw)
In-Reply-To: <c5572997-a94c-dc9e-201b-ad8ad99ab8d8@oracle.com>
On 16/02/17 13:52, Boris Ostrovsky wrote:
>
>
> On 02/16/2017 02:47 AM, 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
>> directory. Default is still /var/run.
>
> As discussed on the other thread, why not make default be the location
> of directory on build system?
Because the build system is not the running system. It doesn't even
have to be the same distro as the intended running system. (If you are
getting adventurous, you can actually build RPMs on Windows 10, and
install them into a CentOS system...)
>
> Or even have it determined at boot time?
Where does this list stop? Should we manually search for the
appropriate /lib, /lib64, /usr/lib, etc to find shared objects?
This is exactly the kind of issue autoconf is intended to solve.
It appears that newer versions of autoconf use --runstatedir for this.
https://lists.gnu.org/archive/html/bug-autoconf/2013-09/msg00002.html
It might be worth following that for forwards compatibility.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-16 14:12 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 [this message]
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
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=358f3ed4-1e65-4023-eb32-eb383694e9e0@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.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).