Changes between Version 41 and Version 42 of current-issues


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

--

Legend:

Unmodified
Added
Removed
Modified
  • current-issues

    v41 v42  
    33== Configuration ==
    44
    5  * Under '''cygwin''' with '''Intel 11 compilers''', the intel compiler might pick up the wrong {{{link.exe}}}, which results in failures setting up the FFLAGS and in failures when linking a binary. 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.
    6    The line to add is of the form
     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
     7Note that on many version of CYGWIN, the default PATH is built using the script /etc/profile, which has the line
     8{{{
     9PATH="/usr/local/bin:/usr/bin:$PATH"
     10}}}
     11which is exactly what you don't want because this puts the CYGWIN version of link ahead of the Windows version in the path! If you change it to
     12{{{
     13PATH="$PATH:/usr/local/bin:/usr/bin"
     14}}}
     15life will be much better.
     16
     17If 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
    718{{{
    819  -Qlocation,link,"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\Bin"
    920}}}
    1021
    11  * '''On MacOS X''', care must be taken regarding the '''Fortran compiler'''.
    12    The [http://hpc.sourceforge.net HPC Mac OS X] page and [http://www.macports.org MacPorts] may offer GNU Fortran compiler.
     22 * '''"./configure: line 20: $'\r': command not found" error on Cygwin.'''  If you see an error like this on Cygwin, it means that your setting for Cygwin is such that the native text style is "Windows" and not "Unix".  As a consequence, the {{{configure}}} and other shell scripts have Window-style line end characters, which cannot be digested properly by the shell.  As a work-around, you can run the "{{{dos2unix}}}" program to correct all failing shell scripts (e.g., by typing "{{{dos2unix configure}}}").  In the long run, we will change the subversion properties for those files to avoid this problem, but it might take some time until all files have been corrected.
     23
     24 * In Windows, the '''CPLEX library link check''' in configure may fail because the CPLEX dll is not found
     25   (configure fails with the error: "Cannot find symbol CPXgetstat with CPX").
     26   Running configure with the option '''{{{--disable-cplex-libcheck}}}''' disables this check.[[BR]]
     27   Just remember to have the CPLEX dll in the path and the {{{ILOG_LICENSE_FILE}}} system variable pointing to the CPLEX license file when executing binaries.
     28
     29 * '''On Mac OS X''', the situation with compilers is a bit of a mess. If you install XCode, you will get the gcc compiler tool chain, but the version is very old and you do not get the GNU Fortran compiler. Installing gfortran from [http://www.macports.org MacPorts] or the [http://hpc.sourceforge.net HPC Mac OS X] should work.
    1330
    1431 * On '''MacOS X''', if you use the Intel 10 compilers and build static (or debug) libraries, it is wise to set F77 to {{{"ifort -shared-intel"}}} to avoid later problems when COIN-OR libraries are linked to each other.
     
    3148   }}}
    3249
    33  * '''"./configure: line 20: $'\r': command not found" error on Cygwin.'''  If you see an error like this on Cygwin, it means that your setting for Cygwin is such that the native text style is "Windows" and not "Unix".  As a consequence, the {{{configure}}} and other shell scripts have Window-style line end characters, which cannot be digested properly by the shell.  As a work-around, you can run the "{{{dos2unix}}}" program to correct all failing shell scripts (e.g., by typing "{{{dos2unix configure}}}").  In the long run, we will change the subversion properties for those files to avoid this problem, but it might take some time until all files have been corrected.
    34 
    35  * [=#MinGWPath] '''When building 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 makeing 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`, 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.
    36 
    3750 * On '''AIX {{{configure}}} runs considerably faster''' if bash is installed and the environment variable {{{CONFIG_SHELL}}} points to it.
    3851   For {{{ksh}}} or {{{bash}}} use
     
    4558   }}}
    4659   before running configure.
    47 
    48  * In Windows, the '''CPLEX library link check''' in configure may fail because the CPLEX dll is not found
    49    (configure fails with the error: "Cannot find symbol CPXgetstat with CPX").
    50    Running configure with the option '''{{{--disable-cplex-libcheck}}}''' disables this check.[[BR]]
    51    Just remember to have the CPLEX dll in the path and the {{{ILOG_LICENSE_FILE}}} system variable pointing to the CPLEX license file when executing binaries.
    5260
    5361