From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-04-15
Date: Tue, 16 Apr 2019 13:44:38 +0200 [thread overview]
Message-ID: <20190416134438.246c63cf@windsurf> (raw)
In-Reply-To: <e6975dfa-1a60-c394-de64-2e11243181d2@micronovasrl.com>
Hello,
On Tue, 16 Apr 2019 12:24:41 +0200
Giulio Benetti <giulio.benetti@micronovasrl.com> wrote:
> > vdr-plugin-vnsiserver-v1.8.0 | 1
>
> This ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ is fixed by:
> https://patchwork.ozlabs.org/patch/1085284/
Yes, but I think https://patchwork.ozlabs.org/patch/1074926/ is a
better fix. This still makes your patch relevant in general, to bump
gettext-tiny and take advantage of the fixes.
In fact in theory, gettext-tiny msg* tools should not even be needed:
gettext-tiny is only used when BR2_SYSTEM_ENABLE_NLS is disabled, and
therefore when we don't want translation files at all. Of course, there
are probably some packages that will still try to call msg* tools when
they don't have an option to disable NLS support. But when they do, we
should preferably use that.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-16 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-04-15 Thomas Petazzoni
2019-04-16 9:47 ` Vadym Kochan
2019-04-16 9:53 ` Vadym Kochan
2019-04-16 10:24 ` Giulio Benetti
2019-04-16 11:44 ` Thomas Petazzoni [this message]
2019-04-16 15:18 ` Giulio Benetti
2019-04-16 20:31 ` Thomas Petazzoni
2019-04-17 9:28 ` Giulio Benetti
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=20190416134438.246c63cf@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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.
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.