On Tue, 12 Jan 2010, Matthew Knepley wrote:
> > I was expecting, once I had found it that is, PETSC_USE_SOCKET_VIEWER
> > and a corresponding configure ability to turn it on/off, might control
> > everything.
> >
>
> This was a bug in the prior release. The fix is to remove the
> PETSC_HAVE_SOCKE
Also - send the relavent configure.log and test.log [if that doesn't
exist - send us log from 'cd src/ksp/ksp/examples/tutorials; make ex2 ex2f'
BTW: Is your goal to reinstall a working version of PETSc?
Satish
On Tue, 12 Jan 2010, Barry Smith wrote:
>
> Does make.log have errors in it? Proba
Does make.log have errors in it? Probably.
This is more a petsc-maint at mcs.anl.gov than a petsc-
dev at mcs.anl.gov email so please move any further discussion if needed
to there.
Barry
On Jan 12, 2010, at 9:05 PM, Kevin.Buckley at ecs.vuw.ac.nz wrote:
>
>>> I am tying to help
Phone: +64 4 463 5971
> Computer Science
> Victoria University of Wellington
> New Zealand
>
>
--
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100112/2baa5cea/attachment.html>
On Tue, 12 Jan 2010, Satish Balay wrote:
> But I'm not sure if this problem still persists on the newer software
> stacks on these machines. I don't remember having to do these edits on
> the NERSC XT4.
I retried a buid on NERSC XT4 and didn't need any manual
edits. Perhaps you can rebuild PETSc
If the computer system (like some of the Cray's) don't provide UNIX
socket support then you cannot use the PETSc socket routines.
Barry
On Jan 12, 2010, at 6:08 PM, Kevin.Buckley at ecs.vuw.ac.nz wrote:
> Hi there,
>
> I am tying to help a researcher here build his application against
On Wed, 13 Jan 2010, Kevin.Buckley at ecs.vuw.ac.nz wrote:
> Hi there,
>
> I am tying to help a researcher here build his application against
> a PETSc (3.0.0 p9) installtion at another site that seems to have
> undefined references to:
>
> PETSC_VIEWER_SOCKET_
Is this unresolved symbol from us
Allison Baker added the comment:
Hi Jed,
You are correct that there is a bug in
HYPRE_BoomerAMGSolveT (which calls hypre_BoomerAMGCycleT) in
Hypre-2.4.0b. It has already been fixed and will be included in the upcoming
beta release.
Thanks,
Allison
Jed Brown hypre Tracker wrote:
> New su
The next time you hg pull petsc-dev make sure you also hg pull in
config/BuildSystem
Barry
