On Mon, Jan 14, 2013 at 1:19 PM, John Peterson wrote:
> On Mon, Jan 14, 2013 at 11:29 AM, Dmitry Karpeev
> wrote:
> > Roy,
> > Yes, the problem was with PETSc's makefile. It existed in the early
> > versions of petsc-3.3,
> > but was fixed by one of the early patches:
> >
> https://bitbucket.or
On Mon, Jan 14, 2013 at 11:29 AM, Dmitry Karpeev wrote:
> Roy,
> Yes, the problem was with PETSc's makefile. It existed in the early
> versions of petsc-3.3,
> but was fixed by one of the early patches:
> https://bitbucket.org/petsc/petsc-dev/diff/makefile?diff2=a0fe59a5123c&at=default
> I was ru
Roy,
Yes, the problem was with PETSc's makefile. It existed in the early
versions of petsc-3.3,
but was fixed by one of the early patches:
https://bitbucket.org/petsc/petsc-dev/diff/makefile?diff2=a0fe59a5123c&at=default
I was running the latest petsc-3.3 and petsc-dev everywhere _except_ the
mach
On Fri, 4 Jan 2013, Roy Stogner wrote:
> On Fri, 4 Jan 2013, John Peterson wrote:
>
>> On Fri, Jan 4, 2013 at 11:22 AM, Dmitry Karpeev
>> wrote:
>
>>> The symptoms are these: configure finds petsc, but leaves PETSCINCLUDEDIRS
>>> and
>>> PETSCLINKLIBS blank, which results in an
>>> insufficient
On Fri, 4 Jan 2013, John Peterson wrote:
> On Fri, Jan 4, 2013 at 11:22 AM, Dmitry Karpeev wrote:
>> The symptoms are these: configure finds petsc, but leaves PETSCINCLUDEDIRS
>> and
>> PETSCLINKLIBS blank, which results in an
>> insufficient libmesh_optional_INCLUDES, which
>> in turn results
On Fri, Jan 4, 2013 at 11:22 AM, Dmitry Karpeev wrote:
> Hi,
> I keep running into an odd problem while configuring libmesh.
> I suspect that it has to do with the way the machine I'm trying to build on
> is configured,
> but I would appreciate any help in tracking down the problem.
>
> The sympto
