public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/30276] gfortran include problem Date: Tue, 02 Jan 2007 15:54:00 -0000 [thread overview] Message-ID: <20070102155430.2242.qmail@sourceware.org> (raw) In-Reply-To: <bug-30276-13793@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from burnus at gcc dot gnu dot org 2007-01-02 15:54 ------- Subject: Bug 30276 Author: burnus Date: Tue Jan 2 15:54:20 2007 New Revision: 120344 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120344 Log: 2007-01-02 Tobias Burnus <burnus@net-b.de> PR fortran/30276 * scanner.c (open_included_file): Support full-path filenames. Modified: trunk/gcc/fortran/ChangeLog trunk/gcc/fortran/scanner.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30276
next prev parent reply other threads:[~2007-01-02 15:54 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-22 10:32 [Bug fortran/30276] New: " aog at terma dot com 2006-12-22 12:56 ` [Bug fortran/30276] " burnus at gcc dot gnu dot org 2006-12-23 14:49 ` steven at gcc dot gnu dot org 2006-12-25 17:55 ` burnus at gcc dot gnu dot org 2006-12-26 12:16 ` tkoenig at gcc dot gnu dot org 2007-01-02 12:51 ` burnus at gcc dot gnu dot org 2007-01-02 15:40 ` patchapp at dberlin dot org 2007-01-02 15:54 ` burnus at gcc dot gnu dot org [this message] 2007-01-02 15:55 ` [Bug fortran/30276] [4.2 only] " burnus at gcc dot gnu dot org 2007-01-04 8:57 ` burnus at gcc dot gnu dot org 2007-01-14 11:45 ` pault at gcc dot gnu dot org 2007-01-30 18:13 ` burnus at gcc dot gnu dot org 2007-01-30 18:15 ` [Bug fortran/30276] " burnus at gcc dot gnu dot org 2007-05-24 1:17 ` pinskia at gcc dot gnu dot org 2007-05-24 1:17 ` pinskia 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=20070102155430.2242.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: 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).