public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwild at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/40010] Parallel make issue when building man pages
Date: Tue, 07 Jul 2009 19:57:00 -0000	[thread overview]
Message-ID: <20090707195726.12487.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40010-17667@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rwild at gcc dot gnu dot org  2009-07-07 19:57 -------
Subject: Bug 40010

Author: rwild
Date: Tue Jul  7 19:57:15 2009
New Revision: 149345

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149345
Log:
gcc/
2009-06-23  Mark Loeser  <mark@halcy0n.com>

        PR build/40010
        * Makefile.in (gcc.pod): Depend on gcc-vers.texi.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/Makefile.in


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40010


  parent reply	other threads:[~2009-07-07 19:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 17:42 [Bug other/40010] New: " halcy0n at gentoo dot org
2009-05-03 17:43 ` [Bug other/40010] " halcy0n at gentoo dot org
2009-07-07 19:57 ` rwild at gcc dot gnu dot org [this message]
2009-07-25 17:53 ` rwild at gcc dot gnu dot org
2009-07-25 17:54 ` rwild at gcc dot gnu dot org

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=20090707195726.12487.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).