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

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

There is a new pull request by fosslinux against master on the void-packages repository

https://github.com/fosslinux/void-packages m4-texinfo
https://github.com/void-linux/void-packages/pull/21162

m4: Add texinfo dependency and fix xlint
```
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
```

A patch file from https://github.com/void-linux/void-packages/pull/21162.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-m4-texinfo-21162.patch --]
[-- Type: text/x-diff, Size: 1172 bytes --]

From 988b682c3235c23f250bcb9846feb0ada264ac21 Mon Sep 17 00:00:00 2001
From: fosslinux <fosslinux@aussies.space>
Date: Mon, 20 Apr 2020 10:08:11 +1000
Subject: [PATCH] m4: Add texinfo dependency and fix xlint

---
 srcpkgs/m4/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/m4/template b/srcpkgs/m4/template
index 111dc6a6b07..c21da25bfad 100644
--- a/srcpkgs/m4/template
+++ b/srcpkgs/m4/template
@@ -2,17 +2,18 @@
 pkgname=m4
 version=1.4.18
 revision=2
-patch_args="-Np1"
 bootstrap=yes
-replaces="chroot-m4>=0"
 build_style=gnu-configure
 configure_args="--enable-changeword --enable-threads"
+hostmakedepends="texinfo" # makeinfo
 short_desc="GNU version of UNIX m4 macro language processor"
-homepage="https://www.gnu.org/software/m4/"
-license="GPL-3.0-or-later"
 maintainer="Enno Boland <gottox@voidlinux.org>"
+license="GPL-3.0-or-later"
+homepage="https://www.gnu.org/software/m4/"
 distfiles="${GNU_SITE}/${pkgname}/${pkgname}-${version}.tar.xz"
 checksum=f2c1e86ca0a404ff281631bdc8377638992744b175afb806e25871a24a934e07
+replaces="chroot-m4>=0"
+patch_args="-Np1"
 
 pre_check() {
 	case "$XBPS_TARGET_MACHINE" in

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  0:14 fosslinux [this message]
2020-04-20  0:37 ` [PR PATCH] [Closed]: WIP: " fosslinux

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21162@inbox.vuxu.org \
    --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).