Here is the relevant part of configure.ac. Who knows what it is supposed to
have there if it isn't correct:
# Now actually check that the C++ compiler works if it is needed.
want_cxx=no
if test $enable_cxx != no; then
test_CXXFLAGS=${CXXFLAGS+set}
echo "CXXFLAGS chosen by autoconf: $CXXFLAGS" >&AC_FD_CC
cxxflags_ac_prog_cxx=$CXXFLAGS
cxxflags_list=ac_prog_cxx
# If the user didn't specify $CXXFLAGS, then try $CFLAGS, with -g removed
# if AC_PROG_CXX thinks that doesn't work. $CFLAGS stands a good chance
# of working, eg. on a GNU system where CC=gcc and CXX=g++.
#
if test "$test_CXXFLAGS" != set; then
cxxflags_cflags=$CFLAGS
cxxflags_list="cflags $cxxflags_list"
if test "$ac_prog_cxx_g" = no; then
cxxflags_cflags=`echo "$cxxflags_cflags" | sed -e 's/ -g //' -e
's/^-g //' -e 's/ -g$//'`
fi
fi
# See if the C++ compiler works. If the user specified CXXFLAGS then all
# we're doing is checking whether AC_PROG_CXX succeeded, since it doesn't
# give a fatal error, just leaves CXX set to a default g++. If on the
# other hand the user didn't specify CXXFLAGS then we get to try here our
# $cxxflags_list alternatives.
#
# Automake includes $CPPFLAGS in a C++ compile, so we do the same here.
#
for cxxflags_choice in $cxxflags_list; do
eval CXXFLAGS=\"\$cxxflags_$cxxflags_choice\"
GMP_PROG_CXX_WORKS($CXX $CPPFLAGS $CXXFLAGS,
[want_cxx=yes
break])
done
# If --enable-cxx=yes but a C++ compiler can't be found, then abort.
if test $want_cxx = no && test $enable_cxx = yes; then
AC_MSG_ERROR([C++ compiler not available, see config.log for details])
fi
fi
AM_CONDITIONAL(WANT_CXX, test $want_cxx = yes)
if test -z "$MPN_PATH"; then
path="$add_path $path"
fi
On 28 March 2014 19:51, Bill Hart <goodwillh...@googlemail.com> wrote:
> Actually, I don't see how this can be right. It would imply that autotools
> was broken, as CXXFLAGS is filled by autotools, not MPIR.
>
> [Well, autotools *is* broken. You have no argument from me there (for
> example, nothing builds in MinGW64 because of this).]
>
> Bill.
>
>
> On 28 March 2014 19:36, Bill Hart <goodwillh...@googlemail.com> wrote:
>
>> I've added it to the list.
>>
>> I'm puzzled as to how this bug has lasted until now to be reported. It
>> must surely have broken things on a lot of C++ platforms, and it almost
>> certainly has never been right.
>>
>> Bill.
>>
>>
>> On 28 March 2014 18:42, leif <not.rea...@online.de> wrote:
>>
>>> On 24.03.2014 17:17, Bill Hart wrote:
>>>
>>>> I have now assigned 36 open tickets to the 2.7 release. I'm sure more
>>>> will be added, but at least we now have some measure of how far we are
>>>> from a release.
>>>>
>>>
>>> Just in case that's not yet on the todo list:
>>>
>>> While --enable-cxx (and 'make check' with that) meanwhile works,
>>> apparently the checks for the C++ compiler's capabilities are currently
>>> missing, such that CXXFLAGS lack the ABI- and machine-specific flags
>>> (-m32/-m64, -march=.../-mtune=...).
>>>
>>>
>>>
>>> -leif
>>>
>>> --
>>> () The ASCII Ribbon Campaign
>>> /\ Help Cure HTML E-Mail
>>>
>>
>>
>
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mpir-devel+unsubscr...@googlegroups.com.
To post to this group, send email to mpir-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/mpir-devel.
For more options, visit https://groups.google.com/d/optout.
