public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>,
		Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject: Re: ISO_Fortran_binding patch
Date: Wed, 09 Jan 2019 23:07:00 -0000	[thread overview]
Message-ID: <CAGkQGiL9MEuXn6oNWL7eXUT_+J-+7EQkZYb0QJdFFMb_MX_++w@mail.gmail.com> (raw)
In-Reply-To: <62d83723-a209-e3ae-ed96-9f4b8c2bed39@netcologne.de>

Hi Thomas,

Aaaah! Light bulb moment - I was looking in the $PREFIX/include directory.

For whatever reason, mine does not appear in lib64 but in lib. OK,
that will have to do for now because the patch is blocking my tree for
a number of other things. I'll fix Bernhard's nit and commit on
Saturday.

Thanks everybody.

Paul

On Wed, 9 Jan 2019 at 20:08, Thomas Koenig <tkoenig@netcologne.de> wrote:
>
> Hi Paul,
>
> > Incidentally, we need to make sure that it is distributed in the
> > include directory. I have yet to figure out how to do that.
>
> It already does that, that was part of what I sent you :-)
>
> It's the
>
> +gfor_c_HEADERS = $(srcdir)/ISO_Fortran_binding.h
> +gfor_cdir =
> $(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include
> +
>
> part in Makefile.am which puts in the requisite magic into
> Makefile.im.
>
> Header files are then installed into
>
> $PREFIX/lib64/gcc/x86_64-pc-linux-gnu/9.0.0/include/ISO_Fortran_binding.h
> $PREFIX/lib64/gcc/x86_64-pc-linux-gnu/9.0.0/32/include/ISO_Fortran_binding.h
>
> So, OK for trunk.
>
> Thanks a lot for this!  Looking at what we are currently
> finishing, I think we will be quite close to F2008 conformance
> when gcc 9 comes out, modulo a few bugs, of course.
>
> Regards
>
>         Thomas
>


-- 
"If you can't explain it simply, you don't understand it well enough"
- Albert Einstein

  parent reply	other threads:[~2019-01-09 23:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 20:29 Paul Richard Thomas
2019-01-08 23:19 ` Thomas Koenig
2019-01-09  9:21   ` Paul Richard Thomas
2019-01-09 20:08     ` Thomas Koenig
2019-01-09 20:37       ` Damian Rouson
2019-01-09 23:07       ` Paul Richard Thomas [this message]
2019-01-12 15:28   ` Paul Richard Thomas
2019-01-12 17:10     ` Steve Kargl
2019-01-12 17:17       ` Steve Kargl
2019-01-12 18:29         ` Paul Richard Thomas
2019-01-12 18:35           ` Paul Richard Thomas
2019-01-14 23:08             ` Jakub Jelinek
2019-01-15  0:08               ` Steve Kargl
2019-01-15  7:06               ` Richard Biener
2019-01-15  8:02                 ` Jakub Jelinek
2019-01-15 19:58                   ` Paul Richard Thomas

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=CAGkQGiL9MEuXn6oNWL7eXUT_+J-+7EQkZYb0QJdFFMb_MX_++w@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sgk@troutmask.apl.washington.edu \
    --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).