From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>, Carlo Zancanaro <carlo@zancanaro.id.au>
Subject: Re: Shepherd release!
Date: Mon, 19 Mar 2018 20:14:32 +0100 [thread overview]
Message-ID: <20180319191432.GA2387@jurong> (raw)
In-Reply-To: <87370wvwyk.fsf@gnu.org>
On Mon, Mar 19, 2018 at 05:42:11PM +0100, Ludovic Courtès wrote:
> You probably need to run ‘gettextize’ first.
That is strange, why have I never heard about this command before?
Anyway, I tried, and it shows a lot of scary warnings:
...
Updating Makefile.am (backup is in Makefile.am~)
Updating configure.ac (backup is in configure.ac~)
Adding an entry to ChangeLog (backup is in ChangeLog~)
Please update po/Makevars so that it defines all the variables mentioned
in po/Makevars.template.
You can then remove po/Makevars.template.
Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
You need aclocal from GNU automake 1.9 (or newer) to do this.
Then run 'autoconf' to regenerate the configure file.
You might also want to copy the convenience header file gettext.h
from the /gnu/store/xd2ifxzy0wah00b4pj83djsqaw03793x-gettext-0.19.8.1/share/gettext directory into your package.
It is a wrapper around <libintl.h> that implements the configure --disable-nls
option.
Press Return to acknowledge the previous three paragraphs.
Then I just went ahead and did "autoreconf -vfi", but this yielded the
following error message:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
configure.ac:86: error: `po/Makefile.in' is already registered with AC_CONFIG_FILES.
../../lib/autoconf/status.m4:288: AC_CONFIG_FILES is expanded from...
configure.ac:86: the top level
autom4te: /gnu/store/mqjjsvkvpbgp9ykmi9jcylzw44qk1hr4-m4-1.4.18/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
Maybe I should follow the advice in the above "three paragraphs"?
$ aclocal -I m4
configure.ac:86: error: `po/Makefile.in' is already registered with AC_CONFIG_FILES.
../../lib/autoconf/status.m4:288: AC_CONFIG_FILES is expanded from...
configure.ac:86: the top level
autom4te: /gnu/store/mqjjsvkvpbgp9ykmi9jcylzw44qk1hr4-m4-1.4.18/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
This looks like the previous analysis by David Pirotte:
On Fri, Mar 16, 2018 at 11:47:24PM -0300, David Pirotte wrote:
> Here there are two problems:
>
> 1- the configure.ac has a tipo
>
> line 86, it has '... po/Makefile.in'
> but it should be '... po/Makefile'
>
> 2- the po subdir does not have a Makefile.in
Andreas
next prev parent reply other threads:[~2018-03-19 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 12:44 Shepherd release! Ludovic Courtès
2018-03-16 13:55 ` Andreas Enge
2018-03-17 2:47 ` David Pirotte
2018-03-19 16:42 ` Ludovic Courtès
2018-03-19 19:14 ` Andreas Enge [this message]
2018-03-20 16:31 ` 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
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=20180319191432.GA2387@jurong \
--to=andreas@enge.fr \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@gnu.org \
--cc=ludo@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).