On Wed, 12 Jul 2000, Lars J. Aas wrote:

> I've just upgraded our projects to CVS Autoconf and CVS Automake.
> It works great on Unix, but on Cygwin, with the VC++ 6.0 compiler, it
> stops on the "C++ compiler working" test, because it doesn't understand
> that "conftest.cc" is a .cpp file so it defaults to "object file" type
> and fails on "corrupted file".  We have to use the filename "conftest.cpp"
> instead.  Will such a switch cause any problems on any other platforms?
> 
>   Lars J


I ran into a problem like the one you describe. It seems
that the CVS version of autoconf does not work with
VC++ at all. When it tries to detect .h files
it fails to find any of them. I was able to trace the
problem down to this bit of code.

ac_try="$ac_cpp conftest.$ac_ext >/dev/null 2>conftest.out"
{ (eval echo configure:1317: \"$ac_try\") >&5; (eval $ac_try) 2>&5; }
ac_err=`grep -v '^ *+' conftest.out | grep -v "^conftest.${ac_ext}\$"`
if test -z "$ac_err"; then
  :
else
  echo "$ac_err" >&5
  echo "configure: failed program was:" >&5
  cat conftest.$ac_ext >&5
  CXXCPP=/lib/cpp
fi


The tests fail for some reason and end up
setting CXXCPP=/lib/cpp. I have a /lib/cpp
file on my linux box, but there is no
such file under Cygwin.

% ls -la /lib/cpp
lrwxrwxrwx    1 root     root           53 Apr 11 01:36 /lib/cpp -> 
../usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/cpp

The result is a bunch of "can not find string.h" type
messages and a config.h that does not work at all.

Mo DeJong
Red Hat Inc

Reply via email to