Looks good to me, so pulled into my branch.
Satish Balay writes:
> I have the following changes in balay/mpiuni-include/jed
>
> - mpi.mod -> mpiuni.mod
>
> - remove -Iinclde/petsc/mpiuni
>
> If ok - they can be pulled into jed/mpiuni-include/maint
>
> Satish
>
> On Wed, 25
I have the following changes in balay/mpiuni-include/jed
- mpi.mod -> mpiuni.mod
- remove -Iinclde/petsc/mpiuni
If ok - they can be pulled into jed/mpiuni-include/maint
Satish
On Wed, 25 Apr 2018, Satish Balay wrote:
> On Wed, 25 Apr 2018, Jed Brown wrote:
>
> > Bitbucket keeps saying
Satish Balay writes:
> On Wed, 25 Apr 2018, Jed Brown wrote:
>
>> Bitbucket keeps saying "Something went wrong while creating your pull
>> request." but you can look at the branch
>>
>> https://bitbucket.org/petsc/petsc/branch/jed/mpiuni-include/maint
>>
>> @balay Can we
On Wed, 25 Apr 2018, Jed Brown wrote:
> Bitbucket keeps saying "Something went wrong while creating your pull
> request." but you can look at the branch
>
> https://bitbucket.org/petsc/petsc/branch/jed/mpiuni-include/maint
>
> @balay Can we simply remove the MPIUNI includes from MPI.py or
Bitbucket keeps saying "Something went wrong while creating your pull
request." but you can look at the branch
https://bitbucket.org/petsc/petsc/branch/jed/mpiuni-include/maint
@balay Can we simply remove the MPIUNI includes from MPI.py or should we
remove it later? What --download packages are
> On Apr 25, 2018, at 2:47 PM, Balay, Satish wrote:
>
> On Wed, 25 Apr 2018, Smith, Barry F. wrote:
>
>>
>>
>>> On Apr 25, 2018, at 2:31 PM, Jed Brown wrote:
>>>
>>> "Smith, Barry F." writes:
>>>
> On Apr 25, 2018, at 1:36
On Wed, 25 Apr 2018, Smith, Barry F. wrote:
>
>
> > On Apr 25, 2018, at 2:31 PM, Jed Brown wrote:
> >
> > "Smith, Barry F." writes:
> >
> >>> On Apr 25, 2018, at 1:36 PM, Jed Brown wrote:
> >>>
> >>> It is currently installed to
> On Apr 25, 2018, at 2:40 PM, Jed Brown wrote:
>
> "Smith, Barry F." writes:
>
>>> On Apr 25, 2018, at 2:31 PM, Jed Brown wrote:
>>>
>>> "Smith, Barry F." writes:
>>>
> On Apr 25, 2018, at 1:36 PM, Jed
"Smith, Barry F." writes:
>> On Apr 25, 2018, at 2:31 PM, Jed Brown wrote:
>>
>> "Smith, Barry F." writes:
>>
On Apr 25, 2018, at 1:36 PM, Jed Brown wrote:
It is currently installed to
> On Apr 25, 2018, at 2:31 PM, Jed Brown wrote:
>
> "Smith, Barry F." writes:
>
>>> On Apr 25, 2018, at 1:36 PM, Jed Brown wrote:
>>>
>>> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
>>> includes it as ,
"Smith, Barry F." writes:
>> On Apr 25, 2018, at 1:36 PM, Jed Brown wrote:
>>
>> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
>> includes it as , which means that users of MPIUNI need to put
>> -I/prefix/include/petsc/mpiuni in
> On Apr 25, 2018, at 1:36 PM, Jed Brown wrote:
>
> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
> includes it as , which means that users of MPIUNI need to put
> -I/prefix/include/petsc/mpiuni in their command lines. Matt and I agree
> that this
Satish Balay writes:
> If we really have to change - I'm inclined towards Matt's prefered approach.
>
> [issues with 'dirty builddir' is a separate problem
I don't care about the build directory, I care about the install
directory. It should be possible to install serial
If we really have to change - I'm inclined towards Matt's prefered approach.
[issues with 'dirty builddir' is a separate problem - it comes up with
switching between replaceable packages [openmpi,mpich,mpiuni] - or
switching versions of the same package]
Satish
On Wed, 25 Apr 2018, Matthew
On Wed, 25 Apr 2018, Jed Brown wrote:
> Satish Balay writes:
>
> > On Wed, 25 Apr 2018, Jed Brown wrote:
> >
> >> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
> >> includes it as , which means that users of MPIUNI need to put
> >>
On Wed, 25 Apr 2018, Jed Brown wrote:
> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
> includes it as , which means that users of MPIUNI need to put
> -I/prefix/include/petsc/mpiuni in their command lines. Matt and I agree
> that this is bad. We disagree on the
On Wed, Apr 25, 2018 at 2:36 PM, Jed Brown wrote:
> It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
> includes it as , which means that users of MPIUNI need to put
> -I/prefix/include/petsc/mpiuni in their command lines. Matt and I agree
> that this is
It is currently installed to include/petsc/mpiuni/mpi.h and petscsys.h
includes it as , which means that users of MPIUNI need to put
-I/prefix/include/petsc/mpiuni in their command lines. Matt and I agree
that this is bad. We disagree on the solution.
He wants to install it to
18 matches
Mail list logo