Adding configure flag
Aurelio Remonda
aurelio.remonda@tallertechnologies.com
Thu Oct 29 18:47:00 GMT 2015
>>> Try using autoreconf, to make sure config.h.in is regenerated
>>> (although I think autoconf should do that anyway).
>>>
I did make autoreconf work but i had to change the autoconf version to 2.69 on:
configure.ac:3 AC_PREREQ(2.69)
override.m4:32 [m4_define([_GCC_AUTOCONF_VERSION], [2.69])])
They were both 2.64 and autoreconf complains about it.
> When libstdc++ is built you should see it print "checking for enabled
> if" (and you should be able to search for that in the
> $target/libstdc++-v3/config.log file)
>
> And then you should see you macro in
> $target/libstdc++-v3/include/$target/bits/c++config.h
It works now :)
>>> GLIBCXX_ENABLE_NEW_OPNT_IF([no])
>>>
>>> Also, I added the following to libstdc++v3's acinclude.m4:
>>>
>>> AC_DEFUN([GLIBCXX_ENABLE_NEW_OPNT_IF], [
>>> GLIBCXX_ENABLE(new-opnt-if,$1,,[enable if on new_opnt instead of while])
>>> if test $enable_new_opnt_if = yes; then
>>> AC_DEFINE(_GLIBCXX_NEW_OPNT_IF, 1,
>>> [Define is new_opnt will be used instead of while.])
>>> fi
>>> AC_MSG_CHECKING([for enabled if])
>>
>> This message isn't very helpful.
Im working on the flag name and the messages, is there any rule for
this? or any personal suggestion?
--
Aurelio Remonda
Software Engineer
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54-351-4217888 / 4218211
More information about the Libstdc++
mailing list