This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: building same source with different flag
- From: Alexandre Duret-Lutz <duret_g at lrde dot epita dot fr>
- To: Ted Irons <ironst at saic dot com>
- Cc: automake at gnu dot org, libtool at gnu dot org, tromey at redhat dot com
- Date: 06 Jan 2002 19:59:55 +0100
- Subject: Re: building same source with different flag
- References: <3C2A9CEB.864A8458@saic.com><2001-12-27-09-29-55+24317+duret_g@epita.fr><3C369831.8D62C1F4@saic.com>
>>> "Ted" == Ted Irons <ironst@saic.com> writes:
[...]
Ted> if test "${lt_cv_prog_compiler_c_o_CXX+set}" = set; then
Ted> echo $ECHO_N "(cached) $ECHO_C" >&6
Ted> else
Ted> lt_cv_prog_compiler_c_o_CXX=no
[...]
Ted> save_CFLAGS="$CFLAGS"
Ted> CFLAGS="$CFLAGS -o out/conftest2.$ac_objext"
[...]
Ted> If I change the CFLAGS to CXXFLAGS in configure the
Ted> configure output gives "g++ supports -c -o file.o
Ted> ... yes"; otherwise the answer given is no. Incidentally,
Ted> configure does a prior check of gcc with -c and -o, and
Ted> that passes.
Ted> I have no idea why the configure check is using CFLAGS instead of
Ted> CXXFLAGS. I changed the CXXFLAGS in ACX_CXXCOMPILE to
Ted> AM_CXXFLAGS, but that made no difference.
It seems this was fixed a few days after libtool 1.4b was
announced. Can you try CVS libtool?
[...]
--
Alexandre Duret-Lutz