From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/vdr-plugin-vnsiserver: needs host-gettext
Date: Thu, 13 Jun 2019 13:28:42 +0200 [thread overview]
Message-ID: <20190613132842.21409a0f@windsurf> (raw)
In-Reply-To: <20190613045042.31272-1-bernd.kuhls@t-online.de>
Hello,
On Thu, 13 Jun 2019 06:50:42 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> msgfmt is needed to build vdr-plugin-vnsiserver
> https://github.com/FernetMenta/vdr-plugin-vnsiserver/blob/master/Makefile#L106
>
> On hosts which provide msgfmt the build succeeds
>
> msgmerge -U --no-wrap --no-location --backup=none -q -N po/lt_LT.po po/vnsiserver.pot
> msgmerge -U --no-wrap --no-location --backup=none -q -N po/de_DE.po po/vnsiserver.pot
> msgfmt -c -o po/lt_LT.mo po/lt_LT.po
> msgfmt -c -o po/de_DE.mo po/de_DE.po
>
> On other systems the build fails:
>
> msgmerge -U --no-wrap --no-location --backup=none -q -N po/de_DE.po po/vnsiserver.pot
> msgmerge -U --no-wrap --no-location --backup=none -q -N po/lt_LT.po po/vnsiserver.pot
> fopen: No such file or directory
> fopen: No such file or directory
>
> Hopefully fixes
> http://autobuild.buildroot.net/results/777/77784c9c169b7cee63ad331c5af9eede1ab0ee00/
> and many others.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
I think we have a better proposal for this:
http://patchwork.ozlabs.org/patch/1074926/. I switched it back to the
"New" state.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-13 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 4:50 [Buildroot] [PATCH 1/1] package/vdr-plugin-vnsiserver: needs host-gettext Bernd Kuhls
2019-06-13 11:28 ` Thomas Petazzoni [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=20190613132842.21409a0f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox