From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: The tricky case of "--localstatedir=/var"
Date: Tue, 16 Feb 2016 17:42:55 -0500 [thread overview]
Message-ID: <87io1oxonk.fsf@netris.org> (raw)
In-Reply-To: <20160216205920.6c7c0684@scratchpost.org> (Danny Milosavljevic's message of "Tue, 16 Feb 2016 20:59:20 +0100")
Danny Milosavljevic <dannym@scratchpost.org> writes:
> also, even worse, when using a fine git checkout for some time, you will from time to time do this:
>
> $ git pull
> $ make check
>
> If this touches stuff autoconf cares about, make will do ./configure
> again and leave localstatedir off. Then lots (32) of the tests will
> fail.
This shouldn't happen, the configure flags should be preserved. It has
never happened to me, and I've been doing "git pull && make" regularly
for a couple of years now.
Can you email bug-guix@gnu.org about your experience here?
Mark
next prev parent reply other threads:[~2016-02-16 22:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 13:57 The tricky case of "--localstatedir=/var" Jookia
2016-02-16 14:29 ` Ricardo Wurmus
2016-02-16 14:52 ` Jookia
2016-02-16 16:41 ` Andreas Enge
2016-02-16 17:12 ` Jookia
2016-02-16 17:16 ` Andreas Enge
2016-02-16 16:04 ` Tobias Geerinckx-Rice
2016-02-16 16:08 ` Tobias Geerinckx-Rice
2016-02-16 19:11 ` Christopher Allan Webber
2016-02-16 19:59 ` Danny Milosavljevic
2016-02-16 22:42 ` Mark H Weaver [this message]
2016-02-17 9:29 ` Ricardo Wurmus
2016-02-17 8:06 ` Chris Marusich
2016-02-17 8:38 ` Jookia
2016-02-17 9:15 ` Chris Marusich
2016-02-17 10:08 ` Jookia
2016-02-17 17:50 ` Chris Marusich
2016-02-17 18:00 ` Jookia
2016-02-17 18:23 ` Andreas Enge
2016-03-17 22:11 ` Ludovic Courtès
2016-03-17 22:19 ` Mathieu Lirzin
2016-03-18 1:12 ` Jookia
2016-03-18 18:45 ` Ludovic Courtès
2016-03-19 3:27 ` Jookia
2016-03-19 14:11 ` Ludovic Courtès
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=87io1oxonk.fsf@netris.org \
--to=mhw@netris.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.