Thanks a lot.<br>But now there is no meaningful output...<br><br>Dominik@Tharsis /cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/src/ksp/ksp/examples/tutorials<br>$ make PETSC_DIR=/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3 PETSC_ARCH=win64-msvc-release ex2<br>
/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe cl -o ex2.o -c -MT -wd4996 -I/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/src/dm/mesh/sieve -I/cygdrive/c/Users/Dominik/Programs/<br>petsc-3.1-p3/win64-msvc-release/include -I/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/include -I/cygdrive/c/Program Files/MPICH2/include -D__INSDIR__=src/ksp/ksp/examples/tutorials/ ex2.c<br>
ex2.c<br>/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe cl -MT -wd4996 -o ex2 ex2.o -L/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/win64-msvc-release/lib -L/cygdrive/c/Users/Dominik/P<br>rograms/petsc-3.1-p3/win64-msvc-release/lib -lpetsc -L/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/win64-msvc-release/lib -lf2clapack -lf2cblas /cygdrive/c/Program\ Files/MPICH2/lib/fmpich2.lib /<br>
cygdrive/c/Program\ Files/MPICH2/lib/fmpich2g.lib /cygdrive/c/Program\ Files/MPICH2/lib/mpi.lib Gdi32.lib User32.lib Advapi32.lib Kernel32.lib Ws2_32.lib<br>/usr/bin/rm -f ex2.o<br><br><br><br><br><br><br><div class="gmail_quote">
On Thu, Jul 22, 2010 at 10:23 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Sorry - you need PETSC_ARCH and PETSC_DIR with make. [normally these are set as env variables]<br>
<br>
make PETSC_DIR=/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3 PETSC_ARCH=win64-msvc-release ex2<br>
<div><div></div><div class="h5"><br>
Satish<br>
<br>
On Thu, 22 Jul 2010, Dominik Szczerba wrote:<br>
<br>
> Hmmm I get the following errors:<br>
><br>
> $ cd src/ksp/ksp/examples/tutorials<br>
><br>
> Dominik@Tharsis/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/src/ksp/ksp/examples/tutorials<br>
> $ make ex2<br>
> makefile:16: /conf/variables: No such file or directory<br>
> makefile:17: /conf/rules: No such file or directory<br>
> makefile:856: /conf/test: No such file or directory<br>
> make: *** No rule to make target `/conf/test'. Stop.<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Thu, Jul 22, 2010 at 10:11 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>> wrote:<br>
><br>
> > Should have said:<br>
> ><br>
> > cd src/ksp/ksp/examples/tutorials<br>
> > make ex2<br>
> > mpiexec -n 2 ./ex2.exe<br>
> > mpiexec -localonly -n 2 ./ex2.exe<br>
> ><br>
> > Satish<br>
> ><br>
> > On Thu, 22 Jul 2010, Satish Balay wrote:<br>
> ><br>
> > > Try running manually. MPICH2 install by default insists on passwd -<br>
> > > and this process isn't handled by petsc scripts properly.<br>
> > ><br>
> > > [or use '--with-mpiexec=mpiexec --localonly']<br>
> > ><br>
> > > Satish<br>
> > ><br>
> > > On Thu, 22 Jul 2010, Dominik Szczerba wrote:<br>
> > ><br>
> > > > Dear all,<br>
> > > ><br>
> > > > The problem was apparently that I was trying to configure Petsc under<br>
> > the 32<br>
> > > > bit terminal with the 64 bit MPI system installation.<br>
> > > ><br>
> > > > I managed to invoke the 64 bit terminal and configure and build Petsc<br>
> > as<br>
> > > > follows:<br>
> > > ><br>
> > > > ./config/configure.py PETSC_DIR=$PWD PETSC_ARCH=win64-msvc-release<br>
> > > > --download-c-blas-lapack=1 --with-x=0 --with-debugging=0<br>
> > --with-cc='win32fe<br>
> > > > cl' --with-fc=0<br>
> > > ><br>
> > > > (with the official MPICH2 64bitinstallation):<br>
> > > ><br>
> > > > MPI:<br>
> > > > Includes: -I/cygdrive/c/Program\ Files/MPICH2/include<br>
> > > > Library: /cygdrive/c/Program\ Files/MPICH2/lib/fmpich2.lib<br>
> > > > /cygdrive/c/Program\ Files/MPICH2/lib/fmpich2g.lib /cygdrive/c/Program\<br>
> > > > Files/MPICH2/lib/mpi.lib<br>
> > > ><br>
> > > > However, I am getting errors when executing "make test": (errors below)<br>
> > > > Any ideas how to proceed? (I clicked some 'yes when Windows popped up a<br>
> > > > yes/no security window)<br>
> > > ><br>
> > > > Regards,<br>
> > > > Dominik<br>
> > > ><br>
> > > ><br>
> > > > $ make PETSC_DIR=/cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3<br>
> > > > PETSC_ARCH=win64-msvc-release test<br>
> > > > Running test examples to verify correct installation<br>
> > > > Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1<br>
> > MPI<br>
> > > > process<br>
> > > > See<br>
> > <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html" target="_blank">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html</a><br>
> > > > Error while connecting to host, No connection could be made because the<br>
> > > > target machine actively refused it. (10061)<br>
> > > > Connect on sock (host=Tharsis, port=8676) failed, exhaused all end<br>
> > points<br>
> > > > Unable to connect to 'Tharsis:8676',<br>
> > > > sock error: Error = -1<br>
> > > ><br>
> > > > Possible error running C/C++ src/snes/examples/tutorials/ex19 with 2<br>
> > MPI<br>
> > > > processes<br>
> > > > See<br>
> > <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html" target="_blank">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html</a><br>
> > > > Error while connecting to host, No connection could be made because the<br>
> > > > target machine actively refused it. (10061)<br>
> > > > Connect on sock (host=Tharsis, port=8676) failed, exhaused all end<br>
> > points<br>
> > > > Unable to connect to 'Tharsis:8676',<br>
> > > > sock error: Error = -1<br>
> > > ><br>
> > > > Completed test examples<br>
> > > ><br>
> > > ><br>
> > > > On Thu, Jul 22, 2010 at 4:13 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>><br>
> > wrote:<br>
> > > ><br>
> > > > > On Thu, 22 Jul 2010, Dominik Szczerba wrote:<br>
> > > > ><br>
> > > > > > Many thanks for your precious feedback.<br>
> > > > > > My MPICH install is 64 bit but it seems that for some reason 32 bit<br>
> > VC<br>
> > > > > > compiler is invoked (I have both 32 and 64 installed).<br>
> > > > ><br>
> > > > > As mentioned - whichever compiler is first in the PATH is used<br>
> > > > > cl<br>
> > > > ><br>
> > > > > > I am clarifying with a local MSVC expert how to control this, will<br>
> > update<br>
> > > > > > you later today.<br>
> > > > ><br>
> > > > > One way to control this - is to run the desired 'build env' cmd - as<br>
> > > > > mentioned in the installation instructions.<br>
> > > > ><br>
> > > > ><br>
> > <a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/installation.html#Windows" target="_blank">http://www.mcs.anl.gov/petsc/petsc-as/documentation/installation.html#Windows</a><br>
> > > > ><br>
> > > > > Satish<br>
> > > > ><br>
> > > > > > Dominik<br>
> > > > > ><br>
> > > > > > On Thu, Jul 22, 2010 at 3:45 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>><br>
> > wrote:<br>
> > > > > ><br>
> > > > > > > > sh: Warning: win32fe: File Not Found: /cygdrive/c/Program<br>
> > > > > > > > Files/MPICH2/lib/amd64/msmpi.lib<br>
> > > > > > ><br>
> > > > > > > Looks like - if win32fe doesn't find the file - it doesn't try to<br>
> > > > > > > convert the path. This is not the cause of his configure failure.<br>
> > > > > > ><br>
> > > > > > > The primary issue is: [which is much ahead in configure.log]<br>
> > > > > > ><br>
> > > > > > > >>>>>>>>>>><br>
> > > > > > > sh:<br>
> > /cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe<br>
> > > > > cl<br>
> > > > > > > -o conftest.exe -MT -wd4996 conftest.o /cygdrive/c/Program\<br>
> > > > > > > Files/MPICH2/lib/mpi.lib Ws2_32.lib<br>
> > > > > > > Executing:<br>
> > > > > > ><br>
> > /cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe cl<br>
> > > > > -o<br>
> > > > > > > conftest.exe -MT -wd4996 conftest.o /cygdrive/c/Program\<br>
> > > > > > > Files/MPICH2/lib/mpi.lib Ws2_32.lib<br>
> > > > > > > sh: conftest.obj : error LNK2019: unresolved external symbol<br>
> > _MPI_Init<br>
> > > > > > > referenced in function _main^M<br>
> > > > > > > C:\Users\Dominik\Programs\PETSC-~1.1-P\conftest.exe : fatal error<br>
> > > > > LNK1120:<br>
> > > > > > > 1 unresolved externals^M<br>
> > > > > > > <<<<<<<<<<<<br>
> > > > > > ><br>
> > > > > > > Here cl is finding the correct library - but not MPI_Init symbol<br>
> > in it.<br>
> > > > > > > For whatever reason - libmpi.lib is not compatible.<br>
> > > > > > ><br>
> > > > > > > Satish<br>
> > > > > > ><br>
> > > > > > > On Thu, 22 Jul 2010, Farshid Mossaiby wrote:<br>
> > > > > > ><br>
> > > > > > > > I doubt 'cl' can interpret Cygwin paths:<br>
> > > > > > > ><br>
> > > > > > > > cl : Command line warning D9002 : ignoring unknown option<br>
> > > > > > > > '/cygdrive/c/Program Files/MPICH2/lib/amd64/msmpi.lib'<br>
> > > > > > > ><br>
> > > > > > > > Shouldn't win32fe convert this path first?<br>
> > > > > > > ><br>
> > > > > > > > Hope this helps.<br>
> > > > > > > ><br>
> > > > > > > > --- On Wed, 7/21/10, Dominik Szczerba <<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>><br>
> > wrote:<br>
> > > > > > > ><br>
> > > > > > > > > From: Dominik Szczerba <<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>><br>
> > > > > > > > > Subject: Re: [petsc-users] configure problems<br>
> > > > > > > > > To: "PETSc users list" <<a href="mailto:petsc-users@mcs.anl.gov">petsc-users@mcs.anl.gov</a>><br>
> > > > > > > > > Date: Wednesday, July 21, 2010, 7:01 PM<br>
> > > > > > > > > Coming back to the original problem:<br>
> > > > > > > > > I tried to compile MPICH2 myself<br>
> > > > > > > > > and failed because of wrong version of automake in Cygwin.<br>
> > > > > > > > > I then<br>
> > > > > > > > > installed the Windows binary available on the mpich2<br>
> > > > > > > > > webpage. I<br>
> > > > > > > > > configure petsc with:<br>
> > > > > > > > ><br>
> > > > > > > > > $ ./config/configure.py PETSC_DIR=$PWD<br>
> > > > > > > > > PETSC_ARCH=win64-msvc-release<br>
> > > > > > > > > --download-c-blas-lapack=1<br>
> > > > > > > > > --with-mpi-dir='/cygdrive/c/Program<br>
> > > > > > > > > Files/MPICH2' --with-x=0 --with-debugging=0<br>
> > > > > > > > > --with-cc='win32fe cl'<br>
> > > > > > > > > --with-fc=0<br>
> > > > > > > > ><br>
> > > > > > > > > to hear at the end (of a very long configuration<br>
> > > > > > > > > process...):<br>
> > > > > > > > ><br>
> > > > > > > > > sh:<br>
> > > > > > > > ><br>
> > /cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe<br>
> > > > > > > > > cl -o conftest.exe -MT -wd4996<br>
> > > > > > > > > conftest.o /cygdrive/c/Program\<br>
> > > > > > > > > Files/MPICH2/lib/amd64/msmpi.lib Ws2_32.lib<br>
> > > > > > > > > Executing:<br>
> > > > > > > > ><br>
> > /cygdrive/c/Users/Dominik/Programs/petsc-3.1-p3/bin/win32fe/win32fe<br>
> > > > > > > > > cl -o conftest.exe -MT -wd4996<br>
> > > > > > > > > conftest.o /cygdrive/c/Program\<br>
> > > > > > > > > Files/MPICH2/lib/amd64/msmpi.lib Ws2_32.lib<br>
> > > > > > > > > sh: Warning: win32fe: File Not Found: /cygdrive/c/Program<br>
> > > > > > > > > Files/MPICH2/lib/amd64/msmpi.lib<br>
> > > > > > > > > cl : Command line warning D9002 : ignoring unknown option<br>
> > > > > > > > > '/cygdrive/c/Program Files/MPICH2/lib/amd64/msmpi.lib'<br>
> > > > > > > > > conftest.obj : error LNK2019: unresolved external symbol<br>
> > > > > > > > > _MPI_Init<br>
> > > > > > > > > referenced in function _main<br>
> > > > > > > > > C:\Users\Dominik\Programs\PETSC-~1.1-P\conftest.exe : fatal<br>
> > > > > > > > > error<br>
> > > > > > > > > LNK1120: 1 unresolved externals<br>
> > > > > > > > ><br>
> > > > > > > > > Any directions why would the configuration look for a<br>
> > > > > > > > > nonexistent<br>
> > > > > > > > > library? The contents of the installation folder are:<br>
> > > > > > > > ><br>
> > > > > > > > > $ ls -la /cygdrive/c/Program\ Files/MPICH2/lib/<br>
> > > > > > > > > total 808<br>
> > > > > > > > > drwx------+ 1 SYSTEM SYSTEM 4096<br>
> > > > > > > > > 2010-07-21 15:54 .<br>
> > > > > > > > > drwx------+ 1 SYSTEM SYSTEM 4096<br>
> > > > > > > > > 2010-07-21 15:54 ..<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 4644<br>
> > > > > > > > > 2010-02-22 17:13 TraceInput.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 322820 2010-02-22 17:09<br>
> > > > > > > > > cxx.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 131316 2010-02-22 17:11<br>
> > > > > > > > > fmpich2.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 136382 2010-02-22 17:13<br>
> > > > > > > > > fmpich2g.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 1936<br>
> > > > > > > > > 2010-02-22 17:13 irlog2rlog.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 10430 2010-02-22 16:30<br>
> > > > > > > > > mpe.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 132128 2010-02-22 16:29<br>
> > > > > > > > > mpi.lib<br>
> > > > > > > > > -rwx------+ 1 SYSTEM SYSTEM 61286 2010-02-22 16:30<br>
> > > > > > > > > rlog.lib<br>
> > > > > > > > ><br>
> > > > > > > > > Best regards,<br>
> > > > > > > > > Dominik<br>
> > > > > > > > ><br>
> > > > > > > > > On Tue, Jul 20, 2010 at 12:44 AM, Jed Brown <<a href="mailto:jed@59a2.org">jed@59a2.org</a>><br>
> > > > > > > > > wrote:<br>
> > > > > > > > > > On Tue, 20 Jul 2010 08:37:18 +1000, Matthew Knepley<br>
> > > > > > > > > <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>><br>
> > > > > > > > > wrote:<br>
> > > > > > > > > >> This would do you absolutely no good. Even Jed's<br>
> > > > > > > > > thing needs all the<br>
> > > > > > > > > >> information that the configure provides. CMake is<br>
> > > > > > > > > exactly what it<br>
> > > > > > > > > >> says, make. It does no configuration<br>
> > > > > > > > > ><br>
> > > > > > > > > > This isn't true, CMake isn't a build system at all, it<br>
> > > > > > > > > does<br>
> > > > > > > > > > configuration and produces build files for another<br>
> > > > > > > > > tool (like make or an<br>
> > > > > > > > > > IDE). I see no point in maintaining duplicate<br>
> > > > > > > > > configuration systems,<br>
> > > > > > > > > > and CMake's scripting language is so attrocious that<br>
> > > > > > > > > "replacing"<br>
> > > > > > > > > > BuildSystem with CMake script would be a disaster.<br>
> > > > > > > > > It's<br>
> > > > > > > > > > cross-compilation support is also a bit weak, and<br>
> > > > > > > > > there are a pile of<br>
> > > > > > > > > > other things that it does poorly (mostly related to<br>
> > > > > > > > > pathologically<br>
> > > > > > > > > > dysfunctional "Find*.cmake" modules). That doesn't<br>
> > > > > > > > > mean it isn't useful<br>
> > > > > > > > > > for producing build files.<br>
> > > > > > > > > ><br>
> > > > > > > > > > Jed<br>
> > > > > > > > > ><br>
> > > > > > > > > ><br>
> > > > > > > > ><br>
> > > > > > > ><br>
> > > > > > > ><br>
> > > > > > > ><br>
> > > > > > > ><br>
> > > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
><br>
<br>
</div></div></blockquote></div><br>