Changes between Version 42 and Version 43 of current-issues


Ignore:
Timestamp:
Nov 2, 2013 8:19:37 PM (6 years ago)
Author:
tkr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • current-issues

    v42 v43  
    33== Configuration ==
    44
    5  * [=#MinGWPath] '''When building with the Visual Studio (cl) or Intel (ifort) compilers on Windows using either the Msys shell or under CYGWIN''', you may see failures that really leave you scratching your head. Before you tear your hair out, check your `PATH`. The problem may be conflicts in the naming of certain utilities provided by Windows and Msys/CYGWIN. They each have utilities called find, link, and sort, but the Windows versions are completely incompatible with the unix versions. It is important that the MSys/CYGWIN versions of find and sort are the ones that come first in your path. You can check this by typing `which find` and `which sort` on the command line and making sure they are the one in the MSys/CYGWIN `bin` directory. If not, make sure that the Msys/CYGWIN `bin` directories come before any Windows system directories in your `PATH`! Both the `configure` and `libtool` shell scripts can fail if this is not true. On the other hand, if you're trying to build with Windows `cl` or Intel `ifort`, then you want the Windows version of `link` to be first in your path, so make sure that the Visual Studio command directories precede the Msys/CYGWIN command directories, which in turn must still precede the Windows system directories. This happens naturally if you run the batch script provided by Visual Studio for setting the environment variables.
    6 
    7 Note that on many version of CYGWIN, the default PATH is built using the script /etc/profile, which has the line
     5 * [=#MinGWPath] '''When building with the Visual Studio (cl) or Intel (ifort) compilers on Windows using either the Msys shell or under CYGWIN''', you may see failures that really leave you scratching your head. Before you tear your hair out, check your `PATH`. The problem may be conflicts in the naming of certain utilities provided by Windows and Msys/CYGWIN. They each have utilities called find, link, and sort, but the Windows versions are completely incompatible with the unix versions. It is important that the MSys/CYGWIN versions of find and sort are the ones that come first in your path. You can check this by typing `which find` and `which sort` on the command line and making sure they are the one in the MSys/CYGWIN `bin` directory. If not, make sure that the Msys/CYGWIN `bin` directories come before any Windows system directories in your `PATH`! Both the `configure` and `libtool` shell scripts can fail if this is not true. On the other hand, if you're trying to build with Windows `cl` or Intel `ifort`, then you want the Windows version of `link` to be first in your path, so make sure that the Visual Studio command directories precede the Msys/CYGWIN command directories, which in turn must still precede the Windows system directories. This happens naturally if you run the batch script provided by Visual Studio for setting the environment variables. Note that on many version of CYGWIN, the default PATH is built using the script /etc/profile, which has the line
    86{{{
    97PATH="/usr/local/bin:/usr/bin:$PATH"
     
    1311PATH="$PATH:/usr/local/bin:/usr/bin"
    1412}}}
    15 life will be much better.
    16 
    17 If you like, you can tell the Intel compilers where to find the right {{{link.exe}}} by editing the files icl.cfg and/or ifort.cfg in the Intel compiler installation. The line to add is of the form
     13life will be much better. If you like, you can tell the Intel compilers where to find the right {{{link.exe}}} by editing the files icl.cfg and/or ifort.cfg in the Intel compiler installation. The line to add is of the form
    1814{{{
    1915  -Qlocation,link,"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Bin"