This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-TM dependency build
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Richard Henderson <rth at redhat dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Aldy Hernandez <aldyh at redhat dot com>, jarias at bsc dot es, Ulrich Drepper <drepper at redhat dot com>, aoliva at redhat dot com
- Date: Fri, 9 Apr 2010 23:16:08 +0100
- Subject: Re: GCC-TM dependency build
- References: <20100331163055.GA2700@redhat.com> <4BBB255B.8000504@bsc.es> <20100406121705.GA6766@redhat.com> <37064.192.168.6.2.1270740237.squirrel@webmail.bsc.es> <20100408153506.GA4966@redhat.com> <4BBE0781.7050907@redhat.com> <20100408164448.GA5771@redhat.com> <4BBE0AED.60407@redhat.com> <20100408165919.GA6093@redhat.com> <4BBF4F2C.4030008@redhat.com>
On 9 April 2010 17:00, Richard Henderson wrote:
>
> I have no idea how to fix this. ?Ideas?
Maybe a dumb question, I don't know the context of this problem...
Is <cassert> the only C++ header that causes a problem?
<cassert> is exactly equivalent to <assert.h> because it only declares
macros, which are not in namespace std anyway.
So if that's the only problem, using <assert.h> instead of <cassert>
would solve it.