From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 24069@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#24069: [PATCHv2] Re: bug#24069: gcc man page is broken
Date: Mon, 02 Oct 2017 16:53:34 +0200 [thread overview]
Message-ID: <871smlppn5.fsf@gnu.org> (raw)
In-Reply-To: <20171002092431.GP26375@macbook42.flashner.co.il> (Efraim Flashner's message of "Mon, 2 Oct 2017 12:24:31 +0300")
Efraim Flashner <efraim@flashner.co.il> skribis:
> I believe this would cause gcc-5 to be rebuilt, which would cause a
> world rebuild, so for the moment we also need a native-inputs entry for
> gcc-5 making sure that nothing changes, ie: that we're only using
> texinfo there, preferably with a note that it should be changed in the
> future. Also, you should take a look at gnu/packages/commencement and
> make sure that we're not adding perl as a native-input for gcc-boot0 or
> for libstdc++, wherever that happens to live (I don't remember off
> hand).
I think this should go to ‘core-updates’.
> I assume it is OK for us to build the man pages for gcc-final (if it
> happens) since this is the gcc used for actually building packages, and
> I believe the one pulled in for gcc-toolchain.
More precisely, building man pages for ‘gcc-boot0’ is pointless and
possibly adds Perl on the graph for no good reason. So if we can
arrange to just have man pages in ‘gcc-final’, we’re good.
Efraim, could you check whether that works for ‘core-updates’?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-10-02 14:54 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871smlppn5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24069@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.