[petsc-users] Directory name with space used by hypre configure

[Satish Balay]

On Wed, 6 Nov 2013, Qin Lu wrote:

> I did read hypre's instructions (no offense, it is not as clear as PETSc's documents), which gives a configure option example for gcc and g++ using the cygwin path, such as 

hypre/README has:

==========================================
HYPRE Installation Information using CMake
==========================================

CMake is another way to build HYPRE that is particularly useful for building the
code on Windows machines.  CMake provides a uniform interface for setting
configuration options on different platforms.  It does not actually build the
code, but generates input for other "native" build systems such as Make (Unix
platforms) or Visual Studio (Windows).  Here are the basic steps:

1. First, ensure that CMake version 2.8.8 or later is installed on the system.

2. To build the library, run CMake on the top-level HYPRE source directory to
   generate files appropriate for the native build system.  To prevent writing
   over the Makefiles in HYPRE's configure/make system above, only out-of-source
   builds are currently allowed with CMake.  Directories 'src/cmbuild' and
   'src/test/cmbuild' are provided in the release for convenience, but
   alternative build directories may be created by the user:

   - Unix: From the 'src/cmbuild' directory, type 'cmake ..'.

   - Windows: Set the source and build directories to 'src' and 'src/cmbuild',
     then click on 'Configure' following by 'Generate'.

3. To complete the build of the library, compile with the native build system:

   - Unix: From the 'src/cmbuild' directory, type 'make install'.

   - Windows Visual Studio: Open the 'hypre' VS solution file generated by CMake
     and build the 'ALL_BUILD' target, then the 'INSTALL' target.

Optional Features:

Various configuration options can be set from within CMake.  Change these as
appropriate, then reconfigure/generate:

- Unix: From the 'src/cmbuild' directory, type 'ccmake ..', change options, then
  type 'c' then 'q'.

- Windows VS: Change options, then click on 'Configure' then 'Generate'.

=====================

> 
> ./configure CC=gcc CXX=g++ CXXFLAGS="O2 -I/cygdrive/c/MPICH2/include/"
> 
> Does this mean that gcc/g++ understand cygwin paths, while icl does not?

yes.

>  But icl worked for me building PETSc using cygwin paths.

Because we provide a wrapper 'win32fe' that translates the paths and
other options to icc notation.

However hypre's configure does not work with win32fe.

Satish