This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/2504: Problems with the new checking code (boost)
- From: pme at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, pme at gcc dot gnu dot org, schmid at snake dot iap dot physik dot tu-darmstadt dot de
- Date: 27 Dec 2001 22:20:13 -0000
- Subject: Re: libstdc++/2504: Problems with the new checking code (boost)
- Reply-to: pme at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, pme at gcc dot gnu dot org, schmid at snake dot iap dot physik dot tu-darmstadt dot de, gcc-gnats at gcc dot gnu dot org
Synopsis: Problems with the new checking code (boost)
State-Changed-From-To: suspended->feedback
State-Changed-By: pme
State-Changed-When: Thu Dec 27 14:20:13 2001
State-Changed-Why:
I just checked this and it works for me. Note that due
to uglification, the checking line must be changed to
__glibcpp_function_requires(_InputIteratorConcept<_InputIterator>);
^^ ^
^^ ^
The header guards were changed back in April. The testcase you gave
compiles for me with or without the guards defined. If <iterator> is
included there is an error due to redefinition of the __distance function,
of course, but the additional parse error no longer occurs.
Can you try a build from the trunk and let me know if causes problems?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2504