Github messages for voidlinux
 help / color / mirror / Atom feed
From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: WIP: m4: Add texinfo dependency and fix xlint
Date: Mon, 20 Apr 2020 02:37:19 +0200	[thread overview]
Message-ID: <20200420003719.HEtcZxNdygEeFOSM4Jo7O0jfAtnG5iCDLjb5YKObUB4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21162@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

There's a closed pull request on the void-packages repository

WIP: m4: Add texinfo dependency and fix xlint
https://github.com/void-linux/void-packages/pull/21162

Description:
```
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
```

      reply	other threads:[~2020-04-20  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  0:14 [PR PATCH] " fosslinux
2020-04-20  0:37 ` fosslinux [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=20200420003719.HEtcZxNdygEeFOSM4Jo7O0jfAtnG5iCDLjb5YKObUB4@z \
    --to=fosslinux@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).