public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26500] New: info/gfortran.info is no longer being installed Date: Tue, 28 Feb 2006 20:23:00 -0000 [thread overview] Message-ID: <bug-26500-231@http.gcc.gnu.org/bugzilla/> (raw) Current CVS trunk no longer installs $prefix/info/gfortran.info, though the Fortran frontend is being built and installed into $prefix/bin/gfortran (so it's not an --enable-languages issues nor missing prerequisites). FreeBSD 5.4, and makeinfo 4.6. -- Summary: info/gfortran.info is no longer being installed Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: gerald at pfeifer dot com GCC host triplet: i386-unknown-freebsd5.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26500
next reply other threads:[~2006-02-28 20:09 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-28 20:23 gerald at pfeifer dot com [this message] 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 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=bug-26500-231@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).