From: Qais Yousef <qais.yousef@arm.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Missing getext dependency in v2.37
Date: Tue, 8 Jun 2021 19:26:54 +0100 [thread overview]
Message-ID: <20210608182654.a2ggwfovdegciwsu@e107158-lin.cambridge.arm.com> (raw)
In-Reply-To: <20210608145032.6xzlt75thp64gpo6@ws.net.home>
On 06/08/21 16:50, Karel Zak wrote:
> On Mon, Jun 07, 2021 at 05:22:49PM +0100, Qais Yousef wrote:
> > While building v2.37 I hit the following build error
> >
> > : --update --no-wrap --previous --lang=ca ca.po util-linux.pot
> > rm -f ca.gmo && : -c --statistics --verbose -o ca.gmo ca.po
> > mv: cannot stat 't-ca.gmo': No such file or directory
>
> The po/ stuff is not required for "make", it's usually necessary for
> "make distcheck" or so. It seems better to keep (x)gettext binary
> installation optional for normal purpose.
>
> There is in ./configure output:
>
> checking whether NLS is requested... yes
> checking for msgfmt... /usr/bin/msgfmt
> checking for gmsgfmt... /usr/bin/msgfmt
> checking for xgettext... no
> checking for msgmerge... /usr/bin/msgmerge
>
> but you're right that it would be nice to have something more verbose.
> I'll add something to ./autogen.sh.
It was just a bit of a head scratch to figure out what went wrong. Wasn't that
big of a deal really at the end, but thought it'd be good to get a better clue
of what went wrong.
>
> > Should configure fail when it detects gettext is missing?
>
> There is difference between what we use as developers (from git repo)
> and what get users by official tarball. The tarball already contains
> compiled .(g)mo files. I guess, as end-user, you do not need to generate
> anything in po/.
Fair enough.
Cheers
--
Qais Yousef
prev parent reply other threads:[~2021-06-08 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 16:22 Missing getext dependency in v2.37 Qais Yousef
2021-06-08 14:50 ` Karel Zak
2021-06-08 18:26 ` Qais Yousef [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210608182654.a2ggwfovdegciwsu@e107158-lin.cambridge.arm.com \
--to=qais.yousef@arm.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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.
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.