<div dir="ltr">On Wed, Jul 10, 2013 at 12:00 AM, Michael Povolotskyi <span dir="ltr"><<a href="mailto:mpovolot@purdue.edu" target="_blank">mpovolot@purdue.edu</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div>Hello everybody,<br>
      unfortunately building petsc without fortran cannot work for me
      because I need MUMPs that requires Scalapack that needs fortran. I
      played with the options. As result the configuration runs okay,
      the build gives an error that does not seem to be related to
      fortran:<br></div></div></blockquote><div><br></div><div style>Quit building with CMake. It complicates everything. Use the legacy build.</div><div style><br></div><div style>   Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div>
      [  0%] Building CXX object
      CMakeFiles/petscsys.dir/src/sys/totalview/tv_data_display.c.o<br>
      Building Fortran object
      CMakeFiles/petscsys.dir/src/sys/f90-mod/petscsysmod.F.o<br>
      Building CXX object
      CMakeFiles/petscsys.dir/src/sys/python/pythonsys.c.o<br>
      [  0%] /usr/include/c++/4.7/bits/stl_algobase.h(60): catastrophic
      error: cannot open source file "bits/c++config.h"<br>
        #include <bits/c++config.h><br>
                                   ^<br>
      <br>
      /usr/include/c++/4.7/bits/stl_algobase.h(60): catastrophic error:
      cannot open source file "bits/c++config.h"<br>
        #include <bits/c++config.h><br>
                                   ^<br>
      <br>
      compilation aborted for
      /home/mpovolot/Code_intel/libs/petsc/build-real/src/sys/info/verboseinfo.c
      (code 4)<br>
      compilation aborted for
      /home/mpovolot/Code_intel/libs/petsc/build-real/src/sys/logging/plog.c
      (code 4)<br>
      <br>
      I attach here the log files.<br>
      Any advise is highly appreciated.<br>
      Michael.<br>
      <br>
      On 7/9/2013 4:34 PM, Matthew Knepley wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">On Tue, Jul 9, 2013 at 3:32 PM, Michael Povolotskyi
        <span dir="ltr"><<a href="mailto:mpovolot@purdue.edu" target="_blank">mpovolot@purdue.edu</a>></span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If I  do
              not need to use petsc in fortran programs, can I build
              petsc without fortran and thus avoid this situation?<br>
              Michael.<br>
              <br>
              <br>
              On 07/09/2013 04:31 PM, Satish Balay wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                For some reason this issue comes up with mpi.mod
                provided by intel<br>
                mpi.<br>
                <br>
                We have a configure test for it - but looks like its not
                sufficient to<br>
                catch this issue.<br>
                <br>
                satish<br>
                <br>
                <br>
                On Tue, 9 Jul 2013, Matthew Knepley wrote:<br>
                <br>
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  On Tue, Jul 9, 2013 at 3:11 PM, Michael Povolotskyi
                  <<a href="mailto:mpovolot@purdue.edu" target="_blank">mpovolot@purdue.edu</a>>wrote:<br>
                  <br>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    Dear Petsc users and developers,<br>
                    I'm trying to build petsc with Intel compiler.<br>
                    <br>
                  </blockquote>
                  1) First, ask yourself whether you really want to
                  build with the Intel<br>
                  compiler. Then ask again.<br>
                  <br>
                  2) Do you need Fortran? If not, turn it off
                  --with-fc=0.<br>
                </blockquote>
              </blockquote>
            </blockquote>
            <div>           
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^</div>
            <div><br>
            </div>
            <div>     Matt</div>
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  3) If you want Fortran and Intel (and have a hatred of
                  free time), try the<br>
                  legacy build<br>
                  <br>
                      make all-legacy<br>
                  <br>
                  4) If this is still broken, send the new make.log<br>
                  <br>
                     Thanks,<br>
                  <br>
                       Matt<br>
                  <br>
                  <br>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    The configuration process runs okay (I attach the
                    log here),<br>
                    but I get an error when I build it:<br>
                    -- Configuring done<br>
                    -- Generating done<br>
                    -- Build files have been written to:
                    /home/mpovolot/Code_intel/**<br>
                    libs/petsc/build-real/linux<br>
                    Scanning dependencies of target petscsys<br>
                    [  0%] [  0%] [  0%] Building CXX object
                    CMakeFiles/petscsys.dir/src/**<br>
                    sys/info/verboseinfo.c.o<br>
                    Building Fortran object
                    CMakeFiles/petscsys.dir/src/**<br>
                    sys/f90-mod/petscsysmod.F.o<br>
                    Building CXX object CMakeFiles/petscsys.dir/src/**<br>
                    sys/totalview/tv_data_display.**c.o<br>
                    Building CXX object CMakeFiles/petscsys.dir/src/**sys/python/pythonsys.c.o<br>
                    Building CXX object CMakeFiles/petscsys.dir/src/**sys/logging/plog.c.o<br>
                    /home/mpovolot/Code_intel/**libs/petsc/build-real/src/sys/**<br>
                    f90-mod/petscsysmod.F:6.11:<br>
                    <br>
                             use mpi<br>
                                1<br>
                    Fatal Error: File 'mpi.mod' opened at (1) is not a
                    GFORTRAN module file<br>
                    make[6]: *** [CMakeFiles/petscsys.dir/src/**sys/f90-mod/petscsysmod.F.o]<br>
                    Error 1<br>
                    make[6]: *** Waiting for unfinished jobs....<br>
                    make[5]: *** [CMakeFiles/petscsys.dir/all] Error 2<br>
                    make[4]: *** [all] Error 2<br>
                    make[3]: *** [ccmake] Error 2<br>
                    make[2]: *** [cmake] Error 2<br>
                    ****************************ERROR**************************************<br>
                       Error during compile, check linux/conf/make.log<br>
                       Send it and linux/conf/configure.log to <a href="mailto:petsc-maint@mcs.anl.gov" target="_blank">petsc-maint@mcs.anl.gov</a><br>
                    ************************************************************************<br>
                    <br>
                    I attach here the make.log<br>
                    What is strange to me that it has something to do
                    with Gfortran, while I<br>
                    want to build everything with Intel.<br>
                    Thank you for help,<br>
                    Michael.<br>
                    <br>
                    --<br>
                    Michael Povolotskyi, PhD<br>
                    Research Assistant Professor<br>
                    Network for Computational Nanotechnology<br>
                    207 S Martin Jischke Drive<br>
                    Purdue University, DLR, room 441-10<br>
                    West Lafayette, Indiana 47907<br>
                    <br>
                    phone: <a href="tel:%2B1-765-494-9396" value="+17654949396" target="_blank">+1-765-494-9396</a><br>
                    fax: <a href="tel:%2B1-765-496-6026" value="+17654966026" target="_blank">+1-765-496-6026</a><br>
                    <br>
                    <br>
                  </blockquote>
                  <br>
                  <br>
                </blockquote>
              </blockquote>
              <br>
            </blockquote>
          </div>
          <br>
          <br clear="all"><span class="HOEnZb"><font color="#888888">
          <div><br>
          </div>
          -- <br>
          What most experimenters take for granted before they begin
          their experiments is infinitely more interesting than any
          results to which their experiments lead.<br>
          -- Norbert Wiener
        </font></span></div>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div><br><br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener
</div></div>