From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] m4, texinfo build failure
Date: Sun, 01 Nov 2020 12:09:16 +0100 [thread overview]
Message-ID: <20201101110916.62asRIChpn2h1DRw3ScWksG-sag_encp4H18MzS667s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21163@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
Closed issue by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/issues/21163
Description:
### System
* xuname: Void 5.6.3_1 x86_64 GenuineIntel uptodate rrFFF
* package:
m4-1.4.18, texinfo-6.7
### Expected behavior
`m4` builds correctly.
### Actual behavior
`m4` fails with:
```
make[2]: Entering directory '/builddir/m4-1.4.18/doc'
MAKEINFO m4.info
/builddir/m4-1.4.18/build-aux/missing: line 81: makeinfo: command not found
WARNING: 'makeinfo' is missing on your system.
You should only need it if you modified a '.texi' file, or
any other file indirectly affecting the aspect of the manual.
You might want to install the Texinfo package:
<http://www.gnu.org/software/texinfo/>
The spurious makeinfo call might also be the consequence of
using a buggy 'make' (AIX, DU, IRIX), in which case you might
want to install GNU make:
<http://www.gnu.org/software/make/>
make[2]: *** [Makefile:1535: m4.info] Error 127
make[2]: Leaving directory '/builddir/m4-1.4.18/doc'
make[1]: *** [Makefile:1572: install-recursive] Error 1
make[1]: Leaving directory '/builddir/m4-1.4.18'
make: *** [Makefile:1867: install] Error 2
```
Adding texinfo to hostmakedepends results in:
```
Making install in doc
make[2]: Entering directory '/builddir/m4-1.4.18/doc'
MAKEINFO m4.info
utf8 "\xAB" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, <FH> line 4254.
utf8 "\xAB" does not map to Unicode at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 1796, <FH> line 4255.
Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3531.
```
### Steps to reproduce the behavior
clone void-packages.
`./xbps-src -N pkg m4` or revbump texinfo and m4 and `./xbps-src pkg m4`.
prev parent reply other threads:[~2020-11-01 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 0:41 [ISSUE] " fosslinux
2020-04-20 11:41 ` rovenmacorp
2020-04-20 12:05 ` rovenmacorp
2020-04-21 0:26 ` fosslinux
2020-04-22 0:33 ` [ISSUE] [CLOSED] " fosslinux
2020-04-25 2:40 ` fosslinux
2020-07-04 10:46 ` LostGhost1
2020-11-01 11:00 ` sgn
2020-11-01 11:09 ` sgn
2020-11-01 11:09 ` sgn [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=20201101110916.62asRIChpn2h1DRw3ScWksG-sag_encp4H18MzS667s@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).