From: David Pirotte <david@altosw.be>
To: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
Cc: 33305@debbugs.gnu.org
Subject: bug#33305: Guile's Autoconf macros play not well with make distcheck
Date: Sat, 10 Nov 2018 19:24:19 -0200 [thread overview]
Message-ID: <20181110192419.20f63772@capac> (raw)
In-Reply-To: <20181110182047.5bb110d5@capac>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
> ...
> There are solution though, here is an example of what I do [1].
Actually, I do this for all the projects maintain, and explain all this in detail on
the Guile-CV install page:
https://www.gnu.org/software/guile-cv/install.html
[ see "Install from ..." and following "Notes:" ...
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-11-10 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 16:07 bug#33305: Guile's Autoconf macros play not well with make distcheck Marc Nieper-Wißkirchen
2018-11-10 20:20 ` David Pirotte
2018-11-10 21:24 ` David Pirotte [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181110192419.20f63772@capac \
--to=david@altosw.be \
--cc=33305@debbugs.gnu.org \
--cc=marc@nieper-wisskirchen.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).