From: HiPhish <hiphish@posteo.de>
To: 49145@debbugs.gnu.org, julien@lepiller.eu
Subject: bug#49145: Cannot build Guix (Texinfo failure)
Date: Mon, 28 Jun 2021 21:27:03 +0000 [thread overview]
Message-ID: <2586453.mvXUDI8C0e@titan> (raw)
In-Reply-To: <10D07CE8-83B9-4CC7-A881-9A29EA908278@lepiller.eu>
Do you mean like this?
$ make --file=doc/local.mk xref_command
doc/local.mk:219: *** missing separator. Stop.
On Saturday, 26 June 2021 12:58:03 CEST Julien Lepiller wrote:
> The process for translating the manual is as follows: we use po4a to replace
> English strings with the target language's strings. At this point, the
> translation contains English node names. Then, the Makefile is supposed to
> replace these with the actual translation of the node names (that way even
> untranslated strings refer to the correct nodes). However, it seems that in
> your case, that process did not go well.
>
> I'd rather try to fix the issue than avoid it, but you can always remove
> references to the translated manual from doc/local.mk.
>
> Can you try running the xref command from doc/local.mk manually, to see if
> it's doing anything wrong?
next prev parent reply other threads:[~2021-06-28 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 21:37 bug#49145: Cannot build Guix (Texinfo failure) HiPhish
2021-06-22 12:06 ` Julien Lepiller
2021-06-22 17:18 ` HiPhish
2021-06-25 22:26 ` HiPhish
2021-06-26 10:58 ` Julien Lepiller
2021-06-28 21:27 ` HiPhish [this message]
2021-07-09 16:21 ` HiPhish
2021-11-10 21:33 ` bug#49145: Solved, I guess HiPhish
2021-11-11 15:59 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2586453.mvXUDI8C0e@titan \
--to=hiphish@posteo.de \
--cc=49145@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).