Oops. That's a typo :) slepc-3.1-p6

So include the PETSC_ARCH/include only if version is greater than 3.1.
I do see the configure script having the information but not sure how
you would propagate that into Make.common.

On Wed, Aug 31, 2011 at 4:51 PM, Vijay S. Mahadevan <[email protected]> wrote:
>> Is this a recent change?  As of slepc-3.0.0-p7 it looks like slepc
>> header files are in $SLEPC_DIR/include.  Also I don't think $PETSC_DIR
>> is required any more as of PETSc 3.
>
> Yes. I have a slepc-3.0.0-p6 installed and it does not require this.
> The inclusion is due to "slepcconf.h" required by "slepcsys.h". And
> slepcconf only exists in the configured include directory. Perhaps you
> could check the slepc version during configure time and include the
> PETSC_ARCH/include only if version is greater than or equal to 3.1 ?
>
> On Wed, Aug 31, 2011 at 3:48 PM, John Peterson <[email protected]> wrote:
>> On Wed, Aug 31, 2011 at 2:21 PM, Vijay S. Mahadevan <[email protected]> 
>> wrote:
>>> All,
>>>
>>> Find attached two small patches for working with the SLEPc dev version.
>>>
>>> One of them is related to adding the include directory in the
>>> configured architecture. And the other is related to the recent change
>>
>> Is this a recent change?  As of slepc-3.0.0-p7 it looks like slepc
>> header files are in $SLEPC_DIR/include.  Also I don't think $PETSC_DIR
>> is required any more as of PETSc 3.
>>
>>> in PETSc where the *Destroy() take the address of the object which has
>>> been propagated in SLEPc to maintain consistency.
>>
>> Looks fine, thanks for sending that in.
>>
>>> Also, I find it strange that the Make.common.in section for SLEPc
>>> computes PETSC_LIB variable. It looks more like a copy-paste error
>>> from the PETSc section. Should it not be SLEPC_LIB ? In any case, it
>>> does not affect the configuration because I believe the
>>> slepc_common_variables that is included defines the correct SLEPC_LIB.
>>> This is true in v3.* and dev but have not checked any previous
>>> versions.
>>
>> This does look like a cut and paste bug, I'll delete those redundant lines...
>>
>> --
>> John
>>
>

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to