This is an old revision of the document!
Unresolved issues
Compiler crash
Oops:
$ gcc -o hello hello.c This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
This rather cryptic message means that “this application” (i.e. gcc) threw an unhandled exception (i.e. an uncaught signal). There can be a million reasons for this, but odds are the problem is simply that gcc failed to create a temporary file. You can confirm this by adding -pipe
to the gcc command line; if it works with -pipe
but not without, the problem is related to temporary files.
Check your $TMP
, $TEMP
and $TMPDIR
variables. At least one of them must be set and point to an existing directory to which you have write access.
Add the following three lines to your ~/.profile
:
export TMPDIR=/tmp export TEMP=/tmp export TMP=/tmp
and paste them into all your open terminals so they will take effect immediately.
There is a looong thread about this issue at http://old.nabble.com/Failed-Install-under-XP-td17636207.html.
LDFLAGS
In order to generate DLLs, libtool needs LDFLAGS=-no-undefined
. We need to
- understand why
- figure out where to handle it
Fortran
not an issue with 3.4.5
/bin/sh ../libtool --tag=F77 --mode=compile gfortran -g -O2 -x f77-cpp-input -c -o getvar.lo getvar.f libtool: compile: gfortran -g -O2 -x f77-cpp-input -c getvar.f -DDLL_EXPORT -o .libs/getvar.o getvar.f:93.65: data cend/ ' ' , '.' , '/' , '$' , '#' , '?' , ',' , ';' , '\\' / 1 Warning: initialization string truncated to match variable at (1) libtool: compile: gfortran -g -O2 -x f77-cpp-input -c getvar.f -o getvar.o >/dev/null 2>&1
This does not happen on Ubuntu, but in all fairness, we're using a different compiler (or, to be exact a different compiler version: gfortran 4.2.4 on Ubuntu, gfortran 4.4.0 on Windows).