public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/101660] [12 Regression] FAIL: gfortran.dg/bind_c_array_params_3.f90
Date: Thu, 29 Jul 2021 07:59:21 +0000 [thread overview]
Message-ID: <bug-101660-4-SbIYyLx2qS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101660-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101660
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think it should be <ISO_Fortran_binding.h> .
Anyway, at least on Fedora it fails because we install the
ISO_Fortran_binding.h
header not to /usr/include but to
/usr/lib/gcc/<target>/<version>/include/ISO_Fortran_binding.h
and so when using xgcc -B ... the just built compiler can't use the system
compiler's version, which IMHO is the only reason why it could succeed for
Sandra or anyone else.
We need an -I ... option that will point the compiler to the libgfortran build
directory (and do so correctly for the current multilib).
next prev parent reply other threads:[~2021-07-29 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 21:18 [Bug fortran/101660] New: " msebor at gcc dot gnu.org
2021-07-29 6:22 ` [Bug fortran/101660] [12 Regression] " rguenth at gcc dot gnu.org
2021-07-29 7:44 ` burnus at gcc dot gnu.org
2021-07-29 7:59 ` jakub at gcc dot gnu.org [this message]
2021-08-01 8:18 ` burnus at gcc dot gnu.org
2021-08-01 8:22 ` burnus at gcc dot gnu.org
2021-08-09 10:36 ` cvs-commit at gcc dot gnu.org
2021-08-09 11:39 ` ubizjak at gmail dot com
2021-08-09 11:48 ` burnus at gcc dot gnu.org
2021-08-10 15:27 ` cvs-commit at gcc dot gnu.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-101660-4-SbIYyLx2qS@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: 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).