Re: Fortran Patches for gcc 5.3.0

David Gressett <[email protected]> Tue, 30 May 2017 17:31:02 +0000
Newsgroups gmane.comp.gnu.mingw.devel
Message-ID <CY1PR13MB063089183B41148905DDE0ACD4F00@CY1PR13MB0630.namprd13.prod.outlook.com>

On Sunday, May 28, 2017 10:48 AM Keith Marshall wrote:

>On 15/03/17 16:04, David Gressett wrote:
>> The bug that is fixed in gcc 6.3.0 is in the GCC Bugzilla as bug
>> report 70684. a patch is in Comment 7:

>Thanks, David, but I wonder is really worth bothering to back-port to
>GCC-5.3.0?  Would it not be better to just release GCC-6.3.0, which we
>have both now built successfully[*]?

It is better; if you are ready to move forward, I say go for it. 

>> The other patch is the one for the undefined items;
>> diff -pNaur gcc-5.3.0-current/libgfortran/Makefile.am gcc-5.3.0-working-m64/libgfortran/Makefile.am
>> ...
>> diff -pNaur gcc-5.3.0-current/libgfortran/Makefile.in gcc-5.3.0-working-m64/libgfortran/Makefile.in

>Strictly, you should patch only Makefile.am, then run autoreconf to
>regenerate Makefile.in, (along with the rest of the build system), and
>yes, that's an absolute pain in the proverbial, unless your automake is
>identically the same version as the original maintainer's; just one of
>the reasons why, despite favouring autoconf, I detest automake.

No disagreement here. I have avoided the autotools, as I have never
needed them for anything that I have produced, and so I know little
about them; I only use them as needed to build open-source software.
For me, they are magic spells, to be avoided when possible.

I have found, however, that I can't avoid automake. My attempt at
rebuilding the various MinGW libraries with my sjlj  GCC-7.1.0 
was derailed when my attempt at compiling gettext-0.18.3.2
dropped dead because it wanted  automake 1.14.

(To  be more specific, it wanted aclocal-1.14)

I am now working on getting the newer automakes to work.

>For me, that patch does no more than suppress an innocuous, and harmless
>warning about only being able to create a static libcaf_single.a; that's
>all I get anyway, with or without the patch.  Does it create a DLL, and
>accompanying libcaf_single.dll.a, for you?

I searched my builds for 5.3.0, 6.3.0, and 7.1.0 and found no DLL.

>[*] I think I've applied all your patches, but I still don't get any
>Ada associated DLLs built.

My builds do not put them in the usual place. Look in

/mingw/lib/gcc/mingw32/6.3.0/adalib

In that directory,  I have libgnarl.a, libgnarl-6.dll, libgnarl-6.dll.a,
libgnat.a, libgnat-6.dll, and libgnat-6.dll.a


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot