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/37821] [4.4 Regression] gfortran is ignoring #includes with the syntax <file.h>
Date: Tue, 14 Oct 2008 12:12:00 -0000	[thread overview]
Message-ID: <20081014121120.12418.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37821-16828@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from burnus at gcc dot gnu dot org  2008-10-14 12:11 -------
Confirm. gcc (the C compiler) has using -I test_directory:

#include "..." search starts here:
#include <...> search starts here:
 test_directory
 /usr/local/include
 /projects/tob/gcc-trunk/include
 /projects/tob/gcc-trunk/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include
 /projects/tob/gcc-trunk/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include-fixed
 /usr/include
End of search list.

whereas gfortran has the following:

#include "..." search starts here:
 test_directory
 /projects/tob/gcc-trunk/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/finclude
 .
#include <...> search starts here:
 /usr/local/include
 /projects/tob/gcc-trunk/include
 /projects/tob/gcc-trunk/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include
 /projects/tob/gcc-trunk/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include-fixed
 /usr/include
End of search list.


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2008-10-14 12:11:19
               date|                            |
            Summary|gfortran is ignoring        |[4.4 Regression] gfortran is
                   |#includes with the syntax   |ignoring #includes with the
                   |<file.h>                    |syntax <file.h>


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


  parent reply	other threads:[~2008-10-14 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  1:48 [Bug fortran/37821] New: " chris dot walter at duke dot edu
2008-10-14  1:51 ` [Bug fortran/37821] " chris dot walter at duke dot edu
2008-10-14  6:28 ` kargl at gcc dot gnu dot org
2008-10-14 12:12 ` burnus at gcc dot gnu dot org [this message]
2008-10-14 12:24 ` [Bug fortran/37821] [4.4 Regression] " dfranke at gcc dot gnu dot org
2008-10-14 12:32 ` burnus at gcc dot gnu dot org
2008-10-14 13:41 ` chris dot walter at duke dot edu
2008-10-15  9:30 ` burnus at gcc dot gnu dot org
2008-11-01 11:41 ` rguenth at gcc dot gnu dot org
2008-11-03  7:23 ` burnus at gcc dot gnu dot org
2008-11-03  7:36 ` burnus 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=20081014121120.12418.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).