On 4/27/2015 8:54 PM, Jeff Squyres (jsquyres) wrote:
Marco --

Have you run into this?

The m4 line in question that seems to be the problem is:

     [AS_VAR_SET(type_var, [`cat conftestval`])]

Does `cat foo` in cygwin result in a ^M in the resulting shell string?  If so, 
is there a standard way to get rid of it?


On cygwin it works fine:

configure:33436: checking size of Fortran CHARACTER
configure:33504: gcc -std=gnu99 -DNDEBUG -ggdb -O2 -pipe -Wimplicit-function-dec laration -fdebug-prefix-map=/pub/devel/openmpi/openmpi-1.8.5rc3-1.x86_64/build=/ usr/src/debug/openmpi-1.8.5rc3-1 -fdebug-prefix-map=/pub/devel/openmpi/openmpi-1 .8.5rc3-1.x86_64/src/openmpi-1.8.5rc3=/usr/src/debug/openmpi-1.8.5rc3-1 -finline
-functions -fno-strict-aliasing -fexceptions -I. -c conftest.c
configure:33511: $? = 0
configure:33521: gfortran -ggdb -O2 -pipe -fdebug-prefix-map=/pub/devel/openmpi/ openmpi-1.8.5rc3-1.x86_64/build=/usr/src/debug/openmpi-1.8.5rc3-1 -fdebug-prefix
-map=/pub/devel/openmpi/openmpi-1.8.5rc3-1.x86_64/src/openmpi-1.8.5rc3=/usr/src/
debug/openmpi-1.8.5rc3-1 -fexceptions conftestf.f90 conftest.o -o conftest -fe
xceptions
configure:33528: $? = 0
configure:33572: ./conftest
configure:33579: $? = 0
configure:33595: result: 1
configure:33618: checking for C type corresponding to CHARACTER

Reply via email to