I forgot to say that I start cygwin from the MSVC 2008 Expresse prompt and that running cl does produce some output (basically prviding an help for the cl function)
2012/8/10 Fabio <fabio.pinna.2006 at gmail.com>: > I followed your advice and I installed the binary version of MPICH for > win 32 bit. > Than I prepared the envirnmental variable with > PETSC_DIR=`pwd`; export PETSC_DIR > > then in the petsc directory > > ./config/configure.py --with-cc='win32fe cl' --with-fc='win32fe f90' > --download-f-blas-lapack --with-mpi-dir=/cygdrive/c/Program\ Files\ > \(x86\)/MPICH2 > > and I got the error > > "C compiler you provided -with-cc win32fe cl does not work" > > Part of the log look like this > > sh: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe cl > -c -o conftest.o conftest.c > Executing: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe > cl -c -o conftest.o conftest.c > sh: Warning: win32fe: Path Not Found: C:\PROGRA~2\MICROS~1.0\SharedIDE\BIN > > conftest.c > > > sh: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe cl > -c -o conftest.o conftest.c > Executing: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe > cl -c -o conftest.o conftest.c > sh: Warning: win32fe: Path Not Found: C:\PROGRA~2\MICROS~1.0\SharedIDE\BIN > > conftest.c > > > Pushing language C > Popping language C > Pushing language Cxx > Popping language Cxx > Pushing language FC > Popping language FC > Pushing language C > Popping language C > sh: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe cl > -o conftest.exe conftest.o > Executing: /cygdrive/d/Workspace/PETSc/petsc-2.3.3-p13/bin/win32fe/win32fe > cl -o conftest.exe conftest.o > sh: Warning: win32fe: Path Not Found: C:\PROGRA~2\MICROS~1.0\SharedIDE\BIN > > LINK : fatal error LNK1104: cannot open file 'kernel32.lib' > > > Possible ERROR while running linker: output: Warning: win32fe: Path > Not Found: C:\PROGRA~2\MICROS~1.0\SharedIDE\BIN > > LINK : fatal error LNK1104: cannot open file 'kernel32.lib' > > ret = 512 > > > > so it look like a directory problem, but the installation is standard, > maybe I cannot use it with MS Visual C++ 2008 Express? > Thank you for your time. > Fabio > > > 2012/8/6 Barry Smith <bsmith at mcs.anl.gov>: >> >> On Aug 5, 2012, at 5:19 PM, Fabio <fabio.pinna.2006 at gmail.com> wrote: >> >>> Thank you for your quick reply,I will try with a reboot. >>> >>> Regarding the compiler my idea was to use MSVC express 2008. I thought >>> it was possible to compile both library with gcc under cygwin. >>> From your reply I guess this is not the case. >>> Does this mean I should compile Petsc with MSVC express as well, isn't it? >> >> Yes, you need to compile PETSc with the compiler you would like to use >> and make sure to use the MPICH binary install since that works with the >> Microsoft compilers. >> >> Barry >> >>> >>> >>> Fabio. >>> >>> >>> >>> 2012/8/5 Satish Balay <balay at mcs.anl.gov>: >>>> On Sun, 5 Aug 2012, Fabio wrote: >>>> >>>>> Dear all, >>>>> I am new to petsc, and I've been struggling with it for the last days. >>>>> >>>>> I want to install it on Windows 7, and first I tried to install the >>>>> Microsoft MPI and then compiling the MPICH. They both seems ok but I >>>>> am not able to compile Petsc with any of them. >>>>> I am mostly interested to MPICH (for portability). >>>>> I used this script to configure >>>>> >>>>> ./config/configure.py PETSC_ARCH=win32-gnu --with-fc=0 >>>>> --download-f2cblaslapack=1 >>>>> ?with-mpi-dir=/cygdrive/d/Workspace/MPICH/mpich2-1.4.1p1 >>>> >>>> What compilers do you plan to use? MS C/C++ or cygwin gcc/g++? >>>> >>>> [MS MPI is for use with MS compiler only. MPICH binary install is for >>>> MS compilers, and MPICH source install is for cygwin gcc/g++] >>>> >>>>> >>>>> and I've got this error, >>>>> >>>>> UNABLE to EXECUTE BINARIES for config/configure.py >>>>> --------------------------------------------------------------------------------------- >>>>> [Errno 16] Device or resource busy: 'conftest.exe' >>>>> >>>>> This error seems to happen pretty randomly at differente places in the >>>>> script. >>>>> Any idea to solve this problem? >>>> >>>> Its bad file locks on windows. The only suggestion we have is reboot. >>>> >>>> For some cygwin issues - you need to run 'rebaseall' but this doesn;t >>>> apper to be >>>> that issue. >>>> >>>> If you still have issues - send the complete log [and logfile] to >>>> petsc-maint. >>>> >>>> Satish >>>> >>>>> Thank you all >>>>> >>>>> Fabio >>>>> >>
