public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/26500] [4.2 Regression] info/gfortran.info is no longer being installed
Date: Wed, 08 Mar 2006 16:11:00 -0000	[thread overview]
Message-ID: <20060308161056.20757.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26500-231@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from bonzini at gnu dot org  2006-03-08 16:10 -------
Subject: Bug 26500

Author: bonzini
Date: Wed Mar  8 16:10:44 2006
New Revision: 111845

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=111845
Log:
2006-03-08  Paolo Bonzini  <bonzini@gnu.org>

        PR bootstrap/26500
        * Makefile.in (dvi, html, install-info): Invoke the corresponding
        language hook targets.
        * ada/Make-lang.in, cp/Make-lang.in, objc/Make-lang.in,
        objcp/Make-lang.in: Create stub rules for dvi, html, install-info
        if language hook targets were missing.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/Makefile.in
    trunk/gcc/ada/Make-lang.in
    trunk/gcc/cp/Make-lang.in
    trunk/gcc/objc/Make-lang.in
    trunk/gcc/objcp/Make-lang.in


-- 


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


  parent reply	other threads:[~2006-03-08 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 20:23 [Bug fortran/26500] New: " gerald at pfeifer dot com
2006-02-28 20:35 ` [Bug fortran/26500] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-02-28 23:12 ` kargl at gcc dot gnu dot org
2006-03-02 10:45 ` bonzini at gnu dot org
2006-03-02 10:47 ` bonzini at gnu dot org
2006-03-06 15:30 ` [Bug bootstrap/26500] " patchapp at dberlin dot org
2006-03-08 16:11 ` bonzini at gcc dot gnu dot org [this message]
2006-03-08 16:11 ` bonzini at 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=20060308161056.20757.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).