Date: Sun, 21 Feb 2016 13:51:28 -0800 (PST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: mexas@bris.ac.uk, thierry@FreeBSD.org Cc: fortran@freebsd.org, freebsd-ports@freebsd.org, tijl@FreeBSD.org Subject: Re: help make port for opencoarrays Message-ID: <201602212151.u1LLpRBB085896@mech-as222.men.bris.ac.uk> In-Reply-To: <20160221164250.GC2122@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>From thierry@pompo.net Sun Feb 21 17:36:47 2016 > >Hello, > >[+ tijl@ to Cc: as maintainer of net/mpich] > >Le mer 17 fév 16 à 23:50:37 +0100, Anton Shterenlikht <mexas@bris.ac.uk> > écrivait : >> Please help/advise >> >> https://github.com/sourceryinstitute/opencoarrays >> >> It requires mpich built with at least gcc5.3, >> more specifically mpif90 built with gcc5.3 or gcc6. >> net/mpich has FORTRAN_USES=fortran, which I understand >> triggers lang/gcc. >> >> Is it a good idea (or at all possible) to add >> an option to net/mpich to choose a particular >> gcc version? >> >> Any other advice? > >ATM Fortran in FreeBSD is in a very bad shape, and, as you know, we >encounter difficulties with several ports (french/aster, cad/salome, >etc.) caused by a mix between clang and Gcc, and thus libstdc++ / >libc++. My impression over the last several years was actually that GCC on FreeBSD has become very stable, at least on amd64. Building ports with complex dependencies is about how GCC integrated with the ports system. So I'd say Fortran itself is all right. Also, I naively thought that ports which use GCC do not use any part of clang. >If building mpich with a newer Gcc could solve the problem with >opencoarrays, I'm afraid it would cause uncompatibilities in other >dependencies - but unfortunately I cannot suggest a better alternative! Well, I'm only asking for an option in the port. The default will not change. I'll have a go locally and see what happens. But I'm not sure what option to use to build with e.g. GCC6. Is it this line? FORTRAN_USES= fortran Or are you saying that building mpich with non-default gcc is problematic because all its dependencies should be built with the same gcc version? Thanks Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201602212151.u1LLpRBB085896>