Having just updated my tree, JMarc's change to configure.in triggered an 
automatic rerun of configure. In the past this has failed to run correctly, 
because configure has insisted on using g++ rather than deccxx. I have, 
therefore, had to run the configure script as 
        CXX=deccxx configure etc

Things have apparently improved (and recently I believe!). All of a sudden 
configure is running as I would hope and things are currently compiling 
nicely.

I have, however, one query. Here is a section of the configure messages:

checking for a good enough C++ compiler... g++
checking for c++... (cached) deccxx
checking whether the C++ compiler (deccxx  ) works... yes

why does it check for g++ at all in this case?

Angus

Reply via email to