From: Xinhui Yang via Grub-devel <grub-devel@gnu.org>
To: grub-devel@gnu.org
Cc: Xinhui Yang <cyan@cyano.uk>
Subject: Strange failure during de_CH.po generation with make -j
Date: Sun, 14 Jan 2024 15:58:42 +0800 [thread overview]
Message-ID: <20240114075841.1585658-1-cyan@cyano.uk> (raw)
Hi,
Recently we observed a strange failure while packaging GRUB 2.12 for
our distro. The translation file generation process might fail if
parallelism was enabled (e.g. `make -j', or with `-j16' and larger
numbers).
We found that the build always failed whilst generating de_CH
translation data from de.po, complaining about syntax errors or a
premature EOF whilst processing the strings. The exact line numbers
msgfilter complained about were random. If we remove de_CH from
linguas.sh, the build passes every time, even with parallelism
enabled - of course, with parallelism disabled, we did not observe
this issue.
This issue has been reproduced on:
- AOSC OS, the aforementioned distro that I work on.
- Debian Bookworm.
I propose the following solutions:
- Tell the distro maintainers not to use -j.
- Patch po/gettext-patches to add a .NOTPARALLEL directive in Makefile.in.in.
We have opted to temporarily disable parallelism in po/Makefile, since we
could not find the culprit to this issue.
Regards,
Xinhui
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2024-01-14 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 7:58 Xinhui Yang via Grub-devel [this message]
2024-01-16 11:21 ` Strange failure during de_CH.po generation with make -j Steve McIntyre
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=20240114075841.1585658-1-cyan@cyano.uk \
--to=grub-devel@gnu.org \
--cc=cyan@cyano.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).