On 10/13/2016 02:31 AM, Satish Balay wrote:
> On Wed, 12 Oct 2016, Satish Balay wrote:
>
>> On Wed, 12 Oct 2016, Antonio Trande wrote:
>>
>>> Latest builds:
>>> http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/petsc/build/464373/
>
>> I'll try and see if I can reproduce this.. [in a 32bit VM
On Thu, 13 Oct 2016, Antonio Trande wrote:
> >>> Latest builds:
> >>> http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/petsc/build/464373/
> >
> >> I'll try and see if I can reproduce this.. [in a 32bit VM]..
> >
> > To start off - I looked at all the 5 32bit build logs in 464373 - and
> >
On Thu, 13 Oct 2016, Antonio Trande wrote:
> New builds:
>
> Without "/usr/lib/rpm/redhat/redhat-hardened-cc1" flags:
> http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/petsc/build/464687/
>
> Same configuration for debugging:
> http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/petsc/bu
On 10/13/2016 04:13 PM, Satish Balay wrote:
> On Thu, 13 Oct 2016, Antonio Trande wrote:
>
> Latest builds:
> http://copr-fe.cloud.fedoraproject.org/coprs/sagitter/petsc/build/464373/
>>>
I'll try and see if I can reproduce this.. [in a 32bit VM]..
>>>
>>> To start off - I looked at a
On Thu, 13 Oct 2016, Antonio Trande wrote:
>
> I guess, we can consider all tests successfully passed.
Great!
I'm sure there will be more issues to deal with [when folks start
using these packages]
For one - with our default build - one uses portable makefile [with
PETSC_DIR/PETSC_ARCH] for de
On 10/13/2016 05:54 PM, Satish Balay wrote:
> On Thu, 13 Oct 2016, Antonio Trande wrote:
>
>>
>> I guess, we can consider all tests successfully passed.
>
> Great!
Thank you very much for your fundamental support.
>
> I'm sure there will be more issues to deal with [when folks start
> using th
