[petsc-users] x64 build problem

2010-01-17 Thread Rob Ellis
Hi Petsc Experts

 

I've been running Petsc/TAO successfully under CVF VC but need to move to 64
bit. Now, I'm trying to compile Petsc on a Windows XP64, VS2008 C/C++ and
IVF 11 from the IVF compiler shell with Cygwin bash using the command

 

./config/configure.py  \

 --with-cc='win32fe cl' \

 --with-cxx='win32fe cl'   \

 --with-fc=ifort\

 --with-mpi-dir=/cygdrive/c/MPICH2 \

 --download-f-blas-lapack=1\

 --with-clanguage=C++ CXXFLAGS='-DMPICH_SKIP_MPICXX -MT -GR -EHsc'

 

and get the following error:

 


=

 Configuring PETSc to compile on your system


=

TESTING: checkCCompiler from
config.setCompilers(/cygdrive/z/ai/petsc-3.0.0-p9/config/BuildSystem/config/
setCompilers.py:394)

 UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for
details):


---

C compiler you provided with -with-cc=win32fe cl does not work


*

 

However if I type cl at the command line, cl seems to work

 

$ cl

Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64

Copyright (C) Microsoft Corporation.  All rights reserved.

 

usage: cl [ option... ] filename... [ /link linkoption... ]

 

 

Any help would be most appreciated.

Cheers,

Rob

 

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20100117/65101131/attachment.htm


[petsc-users] x64 build problem

2010-01-17 Thread Matthew Knepley
You have to send configure.log (send it to petsc-maint at mcs.anl.gov) or we
have absolutely
no idea what is going on.

  Matt

On Sun, Jan 17, 2010 at 7:07 PM, Rob Ellis Robert.G.Ellis at shaw.ca wrote:

  Hi Petsc Experts



 I've been running Petsc/TAO successfully under CVF VC but need to move to
 64 bit. Now, I'm trying to compile Petsc on a Windows XP64, VS2008 C/C++ and
 IVF 11 from the IVF compiler shell with Cygwin bash using the command



 ./config/configure.py  \

  --with-cc='win32fe cl' \

  --with-cxx='win32fe cl'   \

  --with-fc=ifort\

  --with-mpi-dir=/cygdrive/c/MPICH2 \

  --download-f-blas-lapack=1\

  --with-clanguage=C++ CXXFLAGS='-DMPICH_SKIP_MPICXX -MT -GR -EHsc'



 and get the following error:




 =

  Configuring PETSc to compile on your system


 =

 TESTING: checkCCompiler from
 config.setCompilers(/cygdrive/z/ai/petsc-3.0.0-p9/config/BuildSystem/config/setCompilers.py:394)

  UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for
 details):


 ---

 C compiler you provided with -with-cc=win32fe cl does not work


 *



 However if I type cl at the command line, cl seems to work



 $ cl

 Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64

 Copyright (C) Microsoft Corporation.  All rights reserved.



 usage: cl [ option... ] filename... [ /link linkoption... ]





 Any help would be most appreciated.

 Cheers,

 Rob






-- 
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-users/attachments/20100117/adb46af7/attachment.htm


[petsc-users] x64 build problem

2010-01-17 Thread Rob Ellis
Hi Matt,

Of course, my apologies, here it is.

Thanks,

Rob

 

From: petsc-users-boun...@mcs.anl.gov
[mailto:petsc-users-bounces at mcs.anl.gov] On Behalf Of Matthew Knepley
Sent: Sunday, January 17, 2010 5:10 PM
To: PETSc users list
Subject: Re: [petsc-users] x64 build problem

 

You have to send configure.log (send it to petsc-maint at mcs.anl.gov) or we
have absolutely
no idea what is going on.

  Matt

On Sun, Jan 17, 2010 at 7:07 PM, Rob Ellis Robert.G.Ellis at shaw.ca wrote:

Hi Petsc Experts

 

I've been running Petsc/TAO successfully under CVF VC but need to move to 64
bit. Now, I'm trying to compile Petsc on a Windows XP64, VS2008 C/C++ and
IVF 11 from the IVF compiler shell with Cygwin bash using the command

 

./config/configure.py  \

 --with-cc='win32fe cl' \

 --with-cxx='win32fe cl'   \

 --with-fc=ifort\

 --with-mpi-dir=/cygdrive/c/MPICH2 \

 --download-f-blas-lapack=1\

 --with-clanguage=C++ CXXFLAGS='-DMPICH_SKIP_MPICXX -MT -GR -EHsc'

 

and get the following error:

 


=

 Configuring PETSc to compile on your system


=

TESTING: checkCCompiler from
config.setCompilers(/cygdrive/z/ai/petsc-3.0.0-p9/config/BuildSystem/config/
setCompilers.py:394)

 UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for
details):


---

C compiler you provided with -with-cc=win32fe cl does not work


*

 

However if I type cl at the command line, cl seems to work

 

$ cl

Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64

Copyright (C) Microsoft Corporation.  All rights reserved.

 

usage: cl [ option... ] filename... [ /link linkoption... ]

 

 

Any help would be most appreciated.

Cheers,

Rob

 




-- 
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-users/attachments/20100117/b659aa35/attachment-0001.htm
-- next part --
A non-text attachment was scrubbed...
Name: configure.log
Type: application/octet-stream
Size: 33073 bytes
Desc: not available
URL: 
http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20100117/b659aa35/attachment-0001.obj


[petsc-users] x64 build problem

2010-01-17 Thread Barry Smith

Try using the options --with-cc=win32fe --nodetect cl --with- 
cxx=win32fe --nodetect cl instead

This business has to be fixed up very soon in petsc-dev for the  
next release,



Barry

On Jan 17, 2010, at 7:15 PM, Rob Ellis wrote:

 Hi Matt,
 Of course, my apologies, here it is.
 Thanks,
 Rob

 From: petsc-users-bounces at mcs.anl.gov [mailto:petsc-users-bounces at 
 mcs.anl.gov 
 ] On Behalf Of Matthew Knepley
 Sent: Sunday, January 17, 2010 5:10 PM
 To: PETSc users list
 Subject: Re: [petsc-users] x64 build problem

 You have to send configure.log (send it to petsc-maint at mcs.anl.gov)  
 or we have absolutely
 no idea what is going on.

   Matt

 On Sun, Jan 17, 2010 at 7:07 PM, Rob Ellis Robert.G.Ellis at shaw.ca  
 wrote:
 Hi Petsc Experts

 I've been running Petsc/TAO successfully under CVF VC but need to  
 move to 64 bit. Now, I'm trying to compile Petsc on a Windows XP64,  
 VS2008 C/C++ and IVF 11 from the IVF compiler shell with Cygwin bash  
 using the command

 ./config/configure.py  \
  --with-cc='win32fe cl' \
  --with-cxx='win32fe cl'   \
  --with-fc=ifort\
  --with-mpi-dir=/cygdrive/c/MPICH2 \
  --download-f-blas-lapack=1\
  --with-clanguage=C++ CXXFLAGS='-DMPICH_SKIP_MPICXX -MT -GR -EHsc'

 and get the following error:

 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 ==
  Configuring PETSc to compile on your system
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 = 
 ==
 TESTING: checkCCompiler from config.setCompilers(/cygdrive/z/ai/ 
 petsc-3.0.0-p9/config/BuildSystem/config/setCompilers.py:394)
  UNABLE to CONFIGURE with GIVEN OPTIONS(see  
 configure.log for details):
 ---
 C compiler you provided with -with-cc=win32fe cl does not work
 *

 However if I type cl at the command line, cl seems to work

 $ cl
 Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64
 Copyright (C) Microsoft Corporation.  All rights reserved.

 usage: cl [ option... ] filename... [ /link linkoption... ]


 Any help would be most appreciated.
 Cheers,
 Rob




 -- 
 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
 configure.log



[petsc-users] x64 build problem

2010-01-17 Thread Satish Balay
Actually its  --with-cc='win32fe cl --nodetect' --with-fc='win32fe ifort 
--nodetect'  etc..

check 'Using Visual Studio 2005:' section of installation instructions
http://www.mcs.anl.gov/petsc/petsc-as/documentation/installation.html

Satish

On Sun, 17 Jan 2010, Barry Smith wrote:

 
   Try using the options --with-cc=win32fe --nodetect cl --with-cxx=win32fe
 --nodetect cl instead
 
   This business has to be fixed up very soon in petsc-dev for the next
 release,
 
 
 
   Barry
 
 On Jan 17, 2010, at 7:15 PM, Rob Ellis wrote:
 
  Hi Matt,
  Of course, my apologies, here it is.
  Thanks,
  Rob
  
  From: petsc-users-bounces at mcs.anl.gov
  [mailto:petsc-users-bounces at mcs.anl.gov] On Behalf Of Matthew Knepley
  Sent: Sunday, January 17, 2010 5:10 PM
  To: PETSc users list
  Subject: Re: [petsc-users] x64 build problem
  
  You have to send configure.log (send it to petsc-maint at mcs.anl.gov) or we
  have absolutely
  no idea what is going on.
  
   Matt
  
  On Sun, Jan 17, 2010 at 7:07 PM, Rob Ellis Robert.G.Ellis at shaw.ca 
  wrote:
  Hi Petsc Experts
  
  I've been running Petsc/TAO successfully under CVF VC but need to move to 64
  bit. Now, I'm trying to compile Petsc on a Windows XP64, VS2008 C/C++ and
  IVF 11 from the IVF compiler shell with Cygwin bash using the command
  
  ./config/configure.py  \
  --with-cc='win32fe cl' \
  --with-cxx='win32fe cl'   \
  --with-fc=ifort\
  --with-mpi-dir=/cygdrive/c/MPICH2 \
  --download-f-blas-lapack=1\
  --with-clanguage=C++ CXXFLAGS='-DMPICH_SKIP_MPICXX -MT -GR -EHsc'
  
  and get the following error:
  
  =
  Configuring PETSc to compile on your system
  =
  TESTING: checkCCompiler from
  config.setCompilers(/cygdrive/z/ai/petsc-3.0.0-p9/config/BuildSystem/config/setCompilers.py:394)
  UNABLE to CONFIGURE with GIVEN OPTIONS(see configure.log for
  details):
  ---
  C compiler you provided with -with-cc=win32fe cl does not work
  *
  
  However if I type cl at the command line, cl seems to work
  
  $ cl
  Microsoft (R) C/C++ Optimizing Compiler Version 15.00.21022.08 for x64
  Copyright (C) Microsoft Corporation.  All rights reserved.
  
  usage: cl [ option... ] filename... [ /link linkoption... ]
  
  
  Any help would be most appreciated.
  Cheers,
  Rob
  
  
  
  
  -- 
  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
  configure.log