From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Branson, Joshua A" <jbranso@purdue.edu>
Cc: "24069@debbugs.gnu.org" <24069@debbugs.gnu.org>
Subject: bug#24069: gcc man page is broken
Date: Sat, 30 Sep 2017 16:36:55 -0400 [thread overview]
Message-ID: <877ewfx6s8.fsf@gmail.com> (raw)
In-Reply-To: <A8208FE4-7670-4C6F-A587-9802FF4F5758@purdue.edu> (Joshua A. Branson's message of "Thu, 30 Mar 2017 22:22:38 +0000")
"Branson, Joshua A" <jbranso@purdue.edu> writes:
> I can confirm that this bug still exists. The man page is broken as described, but info gcc works just fine.
>
> Thanks,
>
> Joshua
The problem is likely caused by lack of the lack of perl as well as pod2man, as
suggested by gcc's build log:
--8<---------------cut here---------------start------------->8---
echo timestamp > gcc.pod
perl ../../gcc-7.2.0/gcc/../contrib/texi2pod.pl ../../gcc-7.2.0/gcc/doc/invoke.texi > gcc.pod
/gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash: perl: command not found
make[2]: [Makefile:3257: gcc.pod] Error 127 (ignored)
echo timestamp > doc/gcc.1
(pod2man --center="GNU" --release="gcc-7.2.0" --date=2017-08-14 --section=1 gcc.pod > doc/gcc.1.T$$ && \
mv -f doc/gcc.1.T$$ doc/gcc.1) || \
(rm -f doc/gcc.1.T$$ && exit 1)
/gnu/store/kpxi8h3669afr9r1bgvaf9ij3y4wdyyn-bash-minimal-4.4.12/bin/bash: pod2man: command not found
make[2]: [Makefile:3235: doc/gcc.1] Error 1 (ignored)
--8<---------------cut here---------------end--------------->8---
I'm currently rebuilding with those two inputs added, will send a patch
if it fixes the problem.
Maxim
next prev parent reply other threads:[~2017-09-30 20:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 20:23 bug#24069: gcc man page is broken Danny Milosavljevic
2017-03-30 22:22 ` Branson, Joshua A
2017-09-30 20:36 ` Maxim Cournoyer [this message]
2017-10-01 13:39 ` bug#24069: [PATCH] " Maxim Cournoyer
2017-10-01 15:54 ` bug#24069: [PATCHv2] " Maxim Cournoyer
2017-10-02 9:24 ` Efraim Flashner
2017-10-02 14:53 ` Ludovic Courtès
2017-10-02 20:15 ` Maxim Cournoyer
2017-10-03 2:28 ` bug#24069: [PATCHv3] " Maxim Cournoyer
2017-10-03 23:44 ` bug#24069: [PATCHv4] " Maxim Cournoyer
2017-10-31 15:16 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ewfx6s8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=24069@debbugs.gnu.org \
--cc=jbranso@purdue.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).