This is the mail archive of the mailing list for the libstdc++ project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Adding configure flag

>>> Try using autoreconf, to make sure 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: 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 :)

>>> Also, I added the following to libstdc++v3's acinclude.m4:
>>>   GLIBCXX_ENABLE(new-opnt-if,$1,,[enable if on new_opnt instead of while])
>>>   if test $enable_new_opnt_if = yes; then
>>>         [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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]