From: Leo Famulari <leo@famulari.name>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: gnupg: Update to 2.1.16.
Date: Sun, 20 Nov 2016 00:56:06 -0500 [thread overview]
Message-ID: <20161120055605.GA9095@jasmine> (raw)
In-Reply-To: <87k2bz9hd9.fsf@gnu.org>
On Sun, Nov 20, 2016 at 12:31:30AM +0100, Mathieu Lirzin wrote:
> Hi,
>
> Leo Famulari <leo@famulari.name> writes:
>
> > On Sun, Nov 20, 2016 at 12:41:31AM +0200, Efraim Flashner wrote:
> >> Looks like they forgot to bootstrap it then.
> >
> > Because I altered two Makefile.am files in the 'patch-paths' phase, I
> > had to re-do the bootstrap in order for the Makefiles to be regenerated.
> >
> > I'm not an expert on Autotools. Does anyone know if there is a better
> > way?
>
> I have not tried but unless some weird issue, I think you can safely
> replace "/bin/pwd" directly in the generated Makefile(s) instead of the
> Makefile.am sources.
>
> This should fix the Autotools dependency and the warning.
I read a bit more and learned about $GNUPGHOME. `/bin/pwd/` is only
invoked if that variable is unset, so I set it in the test suite, and
it works for me.
And the problem with $HOME not existing, worked around by the set-home
phase, was apparently fixed in:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=38d369de13acb95208a0ed8d1cf82ac19173688f;hp=fde9fa81d3d3b25a929b532cc1960d9d9f454a0c
Which I learned about here:
https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git/commit/?id=bbcd4f60e834c79454d1eaf4adf052f8ff545f99
Pushed as 764c5662211793d381b6c4a85f6a1ef4ad353c3f
next prev parent reply other threads:[~2016-11-21 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 18:32 [PATCH 1/1] gnu: gnupg: Update to 2.1.16 Leo Famulari
2016-11-19 22:41 ` Efraim Flashner
2016-11-19 23:09 ` Leo Famulari
2016-11-19 23:31 ` Mathieu Lirzin
2016-11-20 5:56 ` Leo Famulari [this message]
2016-11-19 23:10 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161120055605.GA9095@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mthl@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).