On Wed, Feb 27, 2013 at 2:09 AM, Dmitry Karpeev wrote:
> Here it is: https://github.com/libMesh/libmesh/pull/51
>
I made some line comments. Did you test this with petsc-3.2 or earlier?
> DMlibMeshCreateXXXDecomposition() is "broken" (produces no decompositions
> at the moment),
> but the API
On Wed, Feb 27, 2013 at 12:05 PM, Jed Brown wrote:
>
> On Wed, Feb 27, 2013 at 2:09 AM, Dmitry Karpeev wrote:
>
>> Here it is: https://github.com/libMesh/libmesh/pull/51
>>
>
> I made some line comments. Did you test this with petsc-3.2 or earlier?
>
I tested with petsc-dev, petsc-3.3 and petsc-3
On Wed, Feb 27, 2013 at 9:31 AM, Dmitry Karpeev wrote:
> I made some line comments. Did you test this with petsc-3.2 or earlier?
>>
> I tested with petsc-dev, petsc-3.3 and petsc-3.2.
>
Can you explain how the preprocessor accepted this line without having
PETSC_VERSION_LE defined?
#if !PETSC_V
On Feb 27, 2013, at 7:53 AM, wrote
>
> I have a user trying to configure libMesh on a Linux cluster but it keeps
> running into problems with TBB. He's not alone as I have also had a few
> other reports of people who still receive error even after adding the
> --diable-tbb flag to the config
On Wed, Feb 27, 2013 at 3:42 PM, Jed Brown wrote:
>
> On Wed, Feb 27, 2013 at 9:31 AM, Dmitry Karpeev wrote:
>
>> I made some line comments. Did you test this with petsc-3.2 or earlier?
>>>
>> I tested with petsc-dev, petsc-3.3 and petsc-3.2.
>>
>
> Can you explain how the preprocessor accepted t
On Wed, Feb 27, 2013 at 11:31 AM, Dmitry Karpeev wrote:
> Sure. petscdmlibmesh assumes !PETSC_VERSION_LESS_THAN(3,3,0) at the very
> top.
>
Okay, I missed that. You could have used an exact match
PETSC_VERSION_(3,3,0) in the conditional.
--
