[petsc-dev] [petsc-maint] compilation error
Barry Smith
bsmith at mcs.anl.gov
Sun Oct 6 15:48:05 CDT 2013
By Jed's schedule we are overdue for a new release. When will that happen? Seems better to include in a release.
What branches are in next and pull requests that need to go into master before a release? Any sane way to list them?
Barry
On Oct 6, 2013, at 12:48 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> Benjamin Ward <b.gray.ward at gmail.com> writes:
>
>> Good Afternoon,
>>
>> Yes, the path exists.
>>
>> I don't think the environment changed. I ran make right after I ran
>> configure.
>>
>> I don't understand why the build depends on gfortran, since I am not using
>> gnu compilers.
>
> I don't know why CMake thinks it's important. You should be able to
> build using 'make all-legacy'.
>
> PETSc devs, do you think it will make sense to merge 'jed/gnumake' into
> 'maint'? It is not an interface difference so it's more a matter of
> whether we think it has become stable enough that the rate of problems
> is lower.
More information about the petsc-dev
mailing list