unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miguel <rosen644835@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Robert Vollmert <rob@vllmrt.net>
Subject: Re: automake warning
Date: Mon, 26 Aug 2019 13:37:51 +0200	[thread overview]
Message-ID: <20190826133751.630f0e5d@gmail.com> (raw)
In-Reply-To: <87r25cki4b.fsf@gnu.org>

Hello,

Ludovic Courtès <ludo@gnu.org>:
> Hello,
> 
> (Digging through old messages…)
> 
> Robert Vollmert <rob@vllmrt.net> skribis:
> 
> > When I run `make` in the guix repository, I always get the following
> > block of warnings at the start:
> >
> > configure.ac:23: warning: The 'AM_PROG_MKDIR_P' macro is
> > deprecated, and its use is discouraged.
> > configure.ac:23: You should use the Autoconf-provided
> > 'AC_PROG_MKDIR_P' macro instead,
> > configure.ac:23: and use > > '$(MKDIR_P)' instead of '$(mkdir_p)'in
> > your Makefile.am files.
> > Makefile.am:613: warning: AM_GNU_GETTEXT used but 'po' not in SUBDIRS  
> 
> This has “always been around” and there’s nothing we can do on our
> side.

Actually this has been fixed in gettext some time ago.  The problem lies
on the following line:

configure.ac:24: AM_GNU_GETTEXT_VERSION([0.18.1])

This line is used by autopoint (called by autoreconf, called by
bootstrap script) to install the macros from that exact version.

The first warning can be removed simply bumping the version to 0.18.2,
which includes that fix.  The newer, the better, but that's the minimal
version change.

> However, one should definitely ping bug-gettext@gnu.org about this, it
> seems silly to have these warnings for years.

The warning left can be silly for Guix, as there are three different
translation domains in a single source code base, so the setup is
inherently more complex.  It is not a bad idea at all for a small/medium
size project to warn the missing po folder when the internationalization
is being set up, as gettext "enforces" the use of recursive make into
the it to get the translations targets; Guix does that not only
once, but twice, and another time with different tools and make rules
for the manual translation.

This point maybe worths a discussion in bug-gettext@gnu.org, at least
to give some way to disable it, but I had to clarify this
beforehand, as guix usage is not the common case and one warning
actually complies with our requested behaviour.

Happy hacking,
Miguel

      reply	other threads:[~2019-08-26 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-20  8:57 automake warning Robert Vollmert
2019-08-22 21:25 ` Ludovic Courtès
2019-08-26 11:37   ` Miguel [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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190826133751.630f0e5d@gmail.com \
    --to=rosen644835@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rob@vllmrt.net \
    /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).