Re: Fortran Patches for gcc 5.3.0

Keith Marshall <[email protected]> Sun, 28 May 2017 16:48:28 +0100
Newsgroups gmane.comp.gnu.mingw.devel
Organization MinGW Project
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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[*]?

> 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.

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 think I've applied all your patches, but I still don't get any 
Ada associated DLLs built.

- -- 
Regards,
Keith.

Public key available from keys.gnupg.net
Key fingerprint: C19E C018 1547 DE50 E1D4 8F53 C0AD 36C6 347E 5A3F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)

iQIcBAEBAgAGBQJZKvFMAAoJEMCtNsY0flo/3wkP/j62TC8UCvrS2gwNg8fO0AEt
/fcCb6OWCpb+9Jkrr1jXykVoDA0liCLK2PpNYpQIPuH1JwRNCMUXL8GDN3lqQpta
T3xlG+ydRz2h8yYdVOAZO5RPo8hmWp2rQDbk7XJt4Klh2ltYHkPfaLtUPDl6nTjc
cXzBmoSG4wBGzjofYxEPlGzCpUOBrvwL6LJ989zVm4NV0JC87fygrcJI17SPPeam
uX2ymKdb06ENPsdNaOQSRbwiCUBvcS8b8Q2ma3bmuzfRAESqzYNTsO5boqD8P4S0
Ps41Y5zkxGoW39dB1o90OPivmFjTBx55mCAEZhWVPdcEA8vGaUeW7Bbo7O1Kf61c
Kb06d9FwX+hBqmQaR68AhHTrXAnjBt3T488NgaFATvGZQhdVE5VesY6ADBkKzGn+
B/NjHpWCdS1Gr4a6xCXUrZWVyBFBI6f4m6V4KS8seLySvoN1+rgmdMmRh6s7oXZP
VWFlCJngytz7IJwrgeULV3gKlMJJFiBKJG03dUnSkPegds135CumomMSb9F3/wlh
Ayo6u0tf9nfcpatfmmeAvDf81EQ9zV0+2S9fPPwuO1YnSR1rN+ZFs6r7x3JVKC6j
CUaNcSO0eCJqVWv6Ay25yg64kFof27xYSa8mSEScUTuPjglx9L2bSzwO6LxHA8V4
Ua+y+xIr6bYzU41nfqls
=GA0c
-----END PGP SIGNATURE-----

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