From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] manual: skip build when perl is unavailable
Date: Fri, 21 Aug 2015 17:17:00 -0000 [thread overview]
Message-ID: <1440177466-16791-1-git-send-email-vapier@gentoo.org> (raw)
In-Reply-To: <200602222112.28242.vapier@gentoo.org>
Do not try to generate the manual when perl is unavailable. This
matches the behavior when makeinfo is unavailable. Otherwise the
install step fails when trying to generate the libm section since
it runs a perl script.
2015-08-21 Mike Frysinger <vapier@gentoo.org>
* manual/Makefile (install): Only build manual when perl is available.
---
manual/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/manual/Makefile b/manual/Makefile
index 5382208..67dff77 100644
--- a/manual/Makefile
+++ b/manual/Makefile
@@ -172,6 +172,7 @@ include ../Rules
.PHONY: install subdir_install install-data
install-data subdir_install: install
+ifneq ($(PERL),no)
ifneq ($(strip $(MAKEINFO)),:)
install: $(inst_infodir)/libc.info
@if $(SHELL) -c '$(INSTALL_INFO) --version' >/dev/null 2>&1; then \
@@ -179,6 +180,7 @@ install: $(inst_infodir)/libc.info
$(INSTALL_INFO) --info-dir=$(inst_infodir) $(inst_infodir)/libc.info;\
else : ; fi
endif
+endif
# Catchall implicit rule for other installation targets from the parent.
install-%: ;
--
2.4.4
next prev parent reply other threads:[~2015-08-21 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 22:58 [patch] skip libm texi generation if perl is not installed Mike Frysinger
2006-02-22 23:50 ` Roland McGrath
2006-02-23 0:18 ` Mike Frysinger
2006-02-23 0:53 ` Roland McGrath
2006-02-23 2:12 ` Mike Frysinger
2006-02-23 17:00 ` Martin Michlmayr
2006-02-23 18:41 ` Mike Frysinger
2015-08-21 17:17 ` Mike Frysinger [this message]
2015-08-21 17:20 ` [PATCH] manual: skip build when perl is unavailable Joseph Myers
2015-08-21 20:07 ` Mike Frysinger
2015-08-21 18:50 ` Florian Weimer
2015-08-21 18:58 ` Dmitry V. Levin
2015-08-21 19:19 ` Mike Frysinger
2015-08-21 19:27 ` Andreas Schwab
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=1440177466-16791-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).