bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release 2.51 now?


From: Ralf Corsepius
Subject: Re: Release 2.51 now?
Date: Tue, 17 Jul 2001 14:10:25 +0200
User-agent: Mozilla/5.0 (X11; U; Linux 2.4.4-64GB-SMP i686; en-US; rv:0.9.1) Gecko/20010714

Akim Demaille wrote:

| : s/AC_TR_CPP/AS_TR_CPP/g
| | Ah... | | Any way to stay compatible with 2.50 and 2.50c until 2.51 is released?

ifndef([AS_TR_CPP], [define([AS_TR_CPP], defn([AC_TR_CPP]))])

| BTW, I think the /lib/cpp problem comes from only running AC_PROG_CXX and | not AC_PROG_CC, which probably means $CC -E won't work - I'll check it out
| now and report back.  Maybe $CXX -E should also be tested?  (or do some
| magic depending on AC_LANG settings?)

It is a very problem which I don't feel we can solve properly now.
CVS Automake should have some bits which help on this issue, but the
safest is definitely to run AC_PROG_CXX first.
No. This doesn't help at all (Cf. my initial hello.cc example, it applied 
AC_PROG_CXX only)


Running AC_PROG_CC first sometimes helps, but it apparently doesn't always help. However, I am inclinded to consider this "pampering with symptoms" and not being an actual cure.

BTW: Meanwhile, after some considerations, I vote for using AC_CHECK_TOOL inside of the check for cpp and to fall back to /lib/cpp as last resort.

Ralf









reply via email to

[Prev in Thread] Current Thread [Next in Thread]