Re: help make port for opencoarrays

[Tijl Coosemans]

On Mon, 22 Feb 2016 09:50:01 + David Chisnall  wrote:
> On 22 Feb 2016, at 09:01, Tijl Coosemans  wrote:
>> I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
>> lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
>> instead of libsupc++.  Maybe David can say more about that (CCed).  
> 
> Ideally, they should be modified to just use libc++.  I thought that bapt
> had done this, but I might have misremembered.

Now I remember he created USES=compiler:gcc-c++11-lib which modifies
CXXFLAGS and LDFLAGS so g++ uses libc++ headers and library.  That works
inside the ports tree but it still leaves g++ cumbersome to use on the
command line.

What about libcompiler_rt, should the gcc ports use that library too
(for its personality function for instance)?

The base system still seems to be using the unwind implementation from
gcc.  Will that change at some point?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: help make port for opencoarrays

[David Chisnall]

On 22 Feb 2016, at 09:01, Tijl Coosemans  wrote:
> 
> I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
> lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
> instead of libsupc++.  Maybe David can say more about that (CCed).

Ideally, they should be modified to just use libc++.  I thought that bapt had 
done this, but I might have misremembered.  Mixing libstdc++ and libc++ is fine 
if both sit on top of libcxxrt and no standard library types cross library 
boundaries, but is problematic otherwise (the good news is that you’ll get 
linker failures if they do try to cross library boundaries, unless they’re 
thrown as exceptions).

David

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: help make port for opencoarrays

[Tijl Coosemans]

On Sun, 21 Feb 2016 13:51:28 -0800 (PST) Anton Shterenlikht  
wrote:
> From thie...@pompo.net Sun Feb 21 17:36:47 2016
>> Le mer 17 f_v 16 _ 23:50:37 +0100, Anton Shterenlikht 
>> _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++.  

I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
instead of libsupc++.  Maybe David can say more about that (CCed).

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

Users can change ports tree default versions by setting DEFAULT_VERSIONS
in /etc/make.conf:

DEFAULT_VERSIONS=   gcc=5

DEFAULT_VERSIONS is handled in /usr/ports/Mk/bsd.default-versions.mk and
/usr/ports/Mk/Uses/fortran.mk uses it to select the Fortran compiler.
So with the line above the Fortran part of net/mpich will be built with
lang/gcc5.

In your opencoarray port I think you can do something like this:

...
USES=   fortran
...
.include 

.if ${GCC_DEFAULT:R} < 5
IGNORE= This port requires that the default GCC version is 5 or higher
.endif
...
.include 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: help make port for opencoarrays

[Anton Shterenlikht]

>From thie...@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 
> é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

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: help make port for opencoarrays

[Thierry Thomas]

Hello,

[+ tijl@ to Cc: as maintainer of net/mpich]

Le mer 17 fév 16 à 23:50:37 +0100, Anton Shterenlikht 
 é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++.

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!
-- 
Th. Thomas.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

help make port for opencoarrays

[Anton Shterenlikht]

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?

Thanks

Anton
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"