If it helps the Debian package, then I would think patching configure.ac
to run CR_PROG_CXX unconditionally is not a problem.
However, I'd not want to accept such a change up-stream until I can
understand WHY calling conditionally is a problem.
-Paul
Alan Woodland wrote:
[snip]
After re-running autoconf the kernel module part fails to build,
during configure with:
configure: error: conditional "am__fastdepCXX" was never defined.
Usually this means the macro was only invoked conditionally.
make: *** [binary-modules] Error 1
configure was called with:
./configure --with-installed-libcr --with-installed-util
--with-components=modules --prefix=/usr --with-linux=2.6.30-1-686
I think this comes from this line of configure.ac:
# If building the tests, we can optionally test C++
if test x"$cr_build_tests" = xyes; then
CR_PROG_CXX
fi
Calling CR_PROG_CXX unconditionally seems to prevent this problem, and
I can't see any obvious negative repercussions for doing so...
I knew there was a reason for not re-running autoconf!
Alan
--
Paul H. Hargrove [email protected]
Future Technologies Group Tel: +1-510-495-2352
HPC Research Department Fax: +1-510-486-6900
Lawrence Berkeley National Laboratory
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
