Re: Build error (no nls)

[Gavin Smith]

On Fri, Aug 20, 2021 at 11:53 PM shoober420 <shoober420@gmail.com> wrote:
> I'm getting a build error when compiling from latest git master as of this 
> email 
> (https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=05261ac09977c25e22a1c58955e11c0041cb3e4d).
>  Im using Gentoo Linux and GCC 11.2 version. full log attached.
>
> make[4]: Leaving directory 
> '/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/po_document'
> ...................... done.
> rm -f ca.us-ascii.gmo && /usr/bin/msgmerge --for-msgfmt -o ca.us-ascii.1po 
> ca.us-ascii.po texinfo_document.pot && /usr/bin/gmsgfmt -c --statistics 
> --verbose -o ca.us-ascii.gmo ca.us-ascii.1po && rm -f ca.us-ascii.1po
> ca.us-ascii.1po: 183 translated messages.
> make[4]: Leaving directory 
> '/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/po_document'
> make[3]: Leaving directory 
> '/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/tp'
> make[2]: *** [Makefile:3577: all-recursive] Error 1
> make[2]: Leaving directory 
> '/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/tp'
> make[1]: *** [Makefile:1473: all-recursive] Error 1
> make[1]: Leaving directory 
> '/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999'
> make: *** [Makefile:1412: all] Error 2

I looked at the log file you sent and it appears to be a problem with
texinfo_document.po. There are many lines like texinfo_document.po

.................................make[5]: Leaving directory
'/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/po_document'
/bin/sh: 10: cannot open texinfo_document.po: No such file
make[5]: *** [Makefile:262: texinfo_document.pot-update] Error 2
make[5]: Leaving directory
'/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/po_document'
.make[4]: *** [Makefile:329: texinfo_document.pot] Error 2
make[4]: Leaving directory
'/var/tmp/portage/sys-apps/texinfo-9999/work/texinfo-9999/po_document'

and "make texinfo_document.pot-update" is run multiple times. I don't
know if this is related to the problem in your other email.