> Okay, I will upload a new PETSc with this fix and the new watch file you
> sent me. Thanks!
Nice. Check it in pbuilder first please - it's working for me, but
it's better if it is tested twice.
> Great. I can't wait to try out the new libmesh with its new elements
> for 4th order Cahn-Hilliar
Hello Ondrej,
Thank you for your detailed inquiry into this issue. I'm glad you got
it working.
On Wed, 2007-11-07 at 23:54 +0100, Ondrej Certik wrote:
> On Nov 7, 2007 9:52 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > > TESTING: checkCxxCompiler from
> > > config.setCompilers(/tmp/buildd/pe
> OK, so petsc seems to be ok now. I am going to try libmesh. Please
> don't close this issue yet - there could be other problems with
> g77/gfortran and maybe the proposed fix is not really a fix (i.e.
> causes other problems). Need to check libmesh out first.
I was able to compile libmesh, with
On Nov 7, 2007 9:52 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> > TESTING: checkCxxCompiler from
> > config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:541)
> > TESTING: checkFortranCompiler from
> > config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSyste
> TESTING: checkCxxCompiler from
> config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:541)
> TESTING: checkFortranCompiler from
> config.setCompilers(/tmp/buildd/petsc-2.3.3/python/BuildSystem/config/setCompilers.py:708)
> *
> I just tried building petsc in my unstable chroot, and it worked fine.
> Perhaps I have a package installed which is not in the Build-Depends?
>
> Here's the post-configure Fortran build info:
>
> Fortran Compiler version:
> -
> Using C/C++ linker:
> Using
Hello Ondrej,
On Fri, 2007-11-02 at 11:22 -0400, Adam C Powell IV wrote:
> I've retitled this bug to your issue, which is an FTBFS, and will try to
> get to it sometime next week. I'll also see if I can build and test
> petsc4py and libmesh using OpenMPI.
>
> On Fri, 2007-11-02 at 02:48 +0100, O
retitle 448158 FTBFS: Fortran MPI check fails
thanks
Hello Ondrej,
This is a separate issue, and should have been a new bug. The limited
platform availability of OpenMPI is a non-issue, and I was about to
close it after a week of inactivity.
I've retitled this bug to your issue, which is an FTB
Package: petsc
--- Please enter the report below this line. ---
Hi Adam,
I have some bad news - I am not able to build the package from source. How to
reproduce:
$ sudo apt-get update
$ apt-get source petsc
$ cd petsc-2.3.3
$ debuild
[...]
TESTING: SGIMPICheck from
config.packages.MPI(/home/o
9 matches
Mail list logo
