I just attempted a build on windows with petsc-3.2 and MS compilers [64bit] - and couldn't reproduce this problem.
$ ./configure --with-cc='win32fe cl' --with-fc=0 --download-f2cblaslapack=1 PETSC_ARCH=arch-mswin64 I'm not sure why this isn't working for you. What do you get for: $ dumpbin.exe /SYMBOLS libf2cblas.lib |grep ddot I see - for my build: balay at bucharest ~/petsc-3.2-p5/arch-mswin64/lib $ dumpbin.exe /SYMBOLS libf2cblas.lib |grep ddot 00A 00000000 SECT4 notype () External | ddot_ 00D 00000000 SECT5 notype Static | $pdata$ddot_ 010 00000000 SECT6 notype Static | $unwind$ddot_ 014 00000004 SECT7 notype Static | ?mp1@?1??ddot_@@9 at 9 (`ddot_'::`2'::mp1) 016 00000010 SECT7 notype Static | ?m@?1??ddot_@@9 at 9 (`ddot_'::`2'::m) 018 00000014 SECT7 notype Static | ?i__@?1??ddot_@@9 at 9 (`ddot_'::`2'::i__) 019 00000000 SECT7 notype Static | ?iy@?1??ddot_@@9 at 9 (`ddot_'::`2'::iy) 01A 00000018 SECT7 notype Static | ?ix@?1??ddot_@@9 at 9 (`ddot_'::`2'::ix) 01B 00000008 SECT7 notype Static | ?dtemp@?1??ddot_@@9 at 9 (`ddot_'::`2'::dtemp) balay at bucharest ~/petsc-3.2-p5/arch-mswin64/lib $ Satish On Mon, 7 Nov 2011, Dominik Szczerba wrote: > Sorry, seems I am wrong, dumpbin.exe says it is valid: > Any more hints are appreciated. > Dominik > > C:\pack\petsc-3.2-p5\win64-msvc-release\lib>dumpbin libf2cblas.lib > Microsoft (R) COFF/PE Dumper Version 10.00.40219.01 > Copyright (C) Microsoft Corporation. All rights reserved. > > > Dump of file libf2cblas.lib > > File Type: LIBRARY > > Summary > > 1668 .bss > 12E2 .data > 5370 .debug$S > 1CD3 .drectve > 17F4 .pdata > BD3 .rdata > 5B191 .text > 2A18 .xdata > > C:\pack\petsc-3.2-p5\win64-msvc-release\lib> > > > On Mon, Nov 7, 2011 at 4:17 PM, Dominik Szczerba <dominik at itis.ethz.ch> > wrote: > > I think I know what the reason is. blas/lapack seems to be linked on > > cygwin as a cygwin library while I need a native Windows library, like > > I am doing with hypre. Is there a way to go here or do I need to (and > > actually can) setup blas/lapack myself? Will it also happen with > > parmetis? Note, parmetis and blas/lapack used to compile fine natively > > some time ago. > > > > Dominik > > > > On Mon, Nov 7, 2011 at 3:57 PM, Dominik Szczerba <dominik at itis.ethz.ch> > > wrote: > >> I am configuring with: > >> > >> ./config/configure.py PETSC_DIR=$PWD PETSC_ARCH=win64-msvc-release > >> --with-x=0 --with-debugging=0 --with-cc='win32fe cl' > >> --with-cxx='win32fe cl' --with-fc=0 --download-f2cblaslapack > >> --with-mpi-dir=/cygdrive/c/mpich2-1.3.2p1-win-x86-64 > >> --with-hypre-dir=/cygdrive/c/pack/hypre-2.7.0b/src/hypre/ > >> --with-parmetis=1 --download-parmetis=1 > >> > >> and getting an error: > >> > >> ******************************************************************************* > >> ? ? ? ? UNABLE to CONFIGURE with GIVEN OPTIONS ? ?(see configure.log > >> for details): > >> ------------------------------------------------------------------------------- > >> --download-f2cblaslapack libraries cannot be used > >> ******************************************************************************* > >> ?File "./config/configure.py", line 283, in petsc_configure > >> ? ?framework.configure(out = sys.stdout) > >> ?File > >> "/cygdrive/c/pack/petsc-3.2-p5/config/BuildSystem/config/framework.py", > >> line 925, in configure > >> ? ?child.configure() > >> ?File > >> "/cygdrive/c/pack/petsc-3.2-p5/config/BuildSystem/config/packages/BlasLapack.py", > >> line 538, in configure > >> ? ?self.executeTest(self.configureLibrary) > >> ?File "/cygdrive/c/pack/petsc-3.2-p5/config/BuildSystem/config/base.py", > >> line 115, in executeTest > >> ? ?ret = apply(test, args,kargs) > >> ?File > >> "/cygdrive/c/pack/petsc-3.2-p5/config/BuildSystem/config/packages/BlasLapack.py", > >> line 444, in configureLibrary > >> ? ?for (name, blasLibrary, lapackLibrary, self.useCompatibilityLibs) > >> in self.generateGuesses(): > >> ?File > >> "/cygdrive/c/pack/petsc-3.2-p5/config/BuildSystem/config/packages/BlasLapack.py", > >> line 162, in generateGuesses > >> ? ?raise RuntimeError('--download-f2cblaslapack libraries cannot be used') > >> > >> I will send the full log to petsc-maint in a second. How do I go from here? > >> > >> Thanks for any hints, > >> Dominik > >> > > > >