From: Olaf Hering <olaf@aepfle.de>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org
Subject: Re: grub.git fails to compiler after gnulib upgrade due to gettext
Date: Tue, 21 May 2019 12:10:33 +0200 [thread overview]
Message-ID: <20190521121033.3fdc37c7.olaf@aepfle.de> (raw)
In-Reply-To: <20190521114932.1362f99c.olaf@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Am Tue, 21 May 2019 11:49:32 +0200
schrieb Olaf Hering <olaf@aepfle.de>:
> Maybe gnulib has just no concept of --disable-nls in the project it serves?
Even if I disable the gettext checks, there is no check to enforce a new enough autoconf.
For short, the toolchain must be updated for the upcoming grub2. Both are not runtime dependencies, so it can not be considered a problem.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-05-21 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 19:26 grub.git fails to compiler after gnulib upgrade due to gettext Olaf Hering
2019-05-21 9:23 ` Daniel Kiper
2019-05-21 9:32 ` Olaf Hering
2019-05-21 9:49 ` Olaf Hering
2019-05-21 10:10 ` Olaf Hering [this message]
2019-05-21 10:20 ` Daniel Kiper
2019-05-21 11:40 ` Colin Watson
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=20190521121033.3fdc37c7.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=dkiper@net-space.pl \
--cc=grub-devel@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.
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.