From: Tobias Burnus <burnus@net-b.de>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] Fix PR 54033, problems with -I, with test cases
Date: Thu, 02 Aug 2012 09:41:00 -0000 [thread overview]
Message-ID: <501A4B12.8070709@net-b.de> (raw)
In-Reply-To: <CAFiYyc0Cwb+qMYC6QQV=5Y0cY+-CN+586pZ446RsCVcnCgMVgg@mail.gmail.com>
On 08/02/2012 10:54 AM, Richard Guenther wrote:
> Seems to break testing, all testcases emit
>
> Warning: Nonexistent include directory "finclude"^M
>
> now and thus all testcases fail like
>
> FAIL: gfortran.dg/alloc_comp_basics_1.f90 -O0 (test for excess errors)
First, I actually wonder why it only lists "finclude" and not the full
pathname.
I think the problem is that gfortran (the driver) passes something like
-fintrinsic-modules-path
/$PREFIX/lib64/gcc/x86_64-unknown-linux-gnu/4.8.0/finclude
to the actual compiler (f951).
That directory only exists if the compiler is installed but not if one
runs the test suite without installing it. I wonder how the OpenMP tests
handle it - there one needs the files from that directory. (It currently
contains the following files: omp_lib.f90 omp_lib.h omp_lib_kinds.mod
omp_lib.mod.) Answer: Theose seemingly include "$BUILD/$triplet/libgomp"
in the -I path, which also contain those files. (That probably clashes
with "use, intrinsic :: omp_lib", but that shouldn't matter.)
I am not sure whether it is the best solution, but one possibility would
be to ignore -fintrinsic-modules-path for the warning. (That assumes
that the warning is (almost) never needed for an installed compiler.)
Tobias
next prev parent reply other threads:[~2012-08-02 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 17:16 [patch, fortran] Fix PR 54033, problems with -I Thomas Koenig
2012-07-26 18:20 ` Janis Johnson
2012-07-27 20:31 ` Thomas Koenig
2012-07-27 22:15 ` Janis Johnson
2012-07-29 12:00 ` [patch, fortran] Fix PR 54033, problems with -I, with test cases Thomas Koenig
2012-07-31 13:50 ` Tobias Burnus
2012-08-02 8:54 ` Richard Guenther
2012-08-02 9:41 ` Tobias Burnus [this message]
2012-08-02 20:08 ` Thomas Koenig
2012-08-03 17:10 ` Thomas Koenig
2012-08-04 17:31 ` H.J. Lu
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=501A4B12.8070709@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=tkoenig@netcologne.de \
/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).