Ah, I think I found the problem. According to the autoconf documentation, AC_CHECK_PROG does nothing if the variable (in this case $check_cpp) is already defined, and it looks like the variable is already defined when that check occurs.
On Sun, Jun 6, 2010 at 6:40 AM, David Matthews < david.matth...@prolingua.co.uk> wrote: > Philip Weaver wrote: > >> Hello. I have noticed that the configure script fails if the CXX >> environment variable is set on OS X. The error message is (when >> CXX=/usr/bin/c++): >> >> checking for /usr/bin/c++... no >> configure: error: No C++ compiler found. Unable to build Poly/ML. >> >> >> This happens when CXX is set to any valid CPP compiler. I'm pretty sure >> it's not user error. >> >> The configure script works fine if CXX is unset or if I bypass the check >> by >> setting check_cpp=yes, as in the following example: >> >> check_cpp=yes CXX=/usr/bin/c++ ./configure >> >> I have confirmed that this happens on at least one other colleague's OS X >> machine. We both have 10.6 Snow Leopard. I have checked both the 5.3 >> release and the latest commit in SVN, and both of them display this >> problem. >> >> Has anyone else encountered this problem? On other operating systems >> besides OS X? >> > > It looks as though it fails in the same way on Linux. I've removed the > check since the build will fail anyway if there's no C++ compiler. > > David > > _______________________________________________ > polyml mailing list > polyml@inf.ed.ac.uk > http://lists.inf.ed.ac.uk/mailman/listinfo/polyml >
_______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
