On Wed, May 01, 2019 at 02:48:30PM -0400, Arvind Sankar wrote: > On Wed, May 01, 2019 at 02:36:10PM -0400, Carlos O'Donell wrote: > > On 5/1/19 2:24 PM, Arvind Sankar wrote: > > > gcc 9 when configured for fortran installs ISO_Fortran_Binding.h in > > > gfor_cdir = > > > $(libdir)/gcc/$(target_alias)/$(gcc_version)$(MULTISUBDIR)/include > > > For x86_64's 32-bit architecture support, this creates a subdirectory > > > named 'include' > > > inside $(libsubdir)/32 which didn't use to exist in gcc 8. > > This doesn't seem correct. > > > > I would have expected the header to exist under the target name, for > > example: > > > > /usr/lib/gcc/i686-redhat-linux/9/include/ISO_Fortran_binding.h > > > > This way it doesn't conflict with other uses. > > > > Perhaps there is enough variability in the way you build, package, and > > install this > > that it can break in some configurations. > > > > I think the gcc community needs to comment on this. > > > > -- > > Cheers, > > Carlos. > > To be clear, it does exist there as well (I think because the native arch has > an > empty MULTISUBDIR. The breakage happens because it _also_ exists under > .../9/32/include.
Including Paul -- looks like the file gets installed in different places in fortran-dev branch vs trunk?
