> But ultimately there is a tight coupling between OpenCoarrays and GFortran;
> it would be good to integrate OpenCoarrays into the GFortran testing
> process... so that you can see when GFortran devs do something that triggers
> a bug in OpenCoarrays, or that has a side effect of breaking OpenC
> I have not encountered a system without cmake yet, I did test the script with
> my
> cmake missing to confirm that it does actually build cmake if needed before it
> proceeds, and then uses make. We have bash scripts already in libgfortran that
> get invoked either during configuration or by bui
On 01/28/2017 03:22 AM, FX wrote:
> Hi Damian,
>
>> It would be difficult or impossible for several OpenCoarrays
>> developers to contribute without OpenCoarrays remaining separate for
>> several reasons.
>
> No, I understand that. What I meant is: do want to provide seamless
> integration, so t
Hi Damian,
> It would be difficult or impossible for several OpenCoarrays
> developers to contribute without OpenCoarrays remaining separate for
> several reasons.
No, I understand that. What I meant is: do want to provide seamless
integration, so that libgfortran builds would automatically dete
