2008/1/26, Jonathan Wakely <[EMAIL PROTECTED]>:
> On 22/01/2008, Christian Joensson wrote:
> > 2008/1/21, Jonathan Wakely
> > > My first guess would be that you've somehow got the C++0x and TR1
> > > versions of boost_sp_shared_count.h mixed up and you're including the
> > > wrong one.
> >
> > well, the testsuite results are posted at, e.g.,
> >
> > http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg00956.html
> >
> > and the libstdc++.log file is attached, compressed using bzip2 -9
>
> Thanks, Christian.
>
> I've CC'd the libstdc++ mailing list, I'll leave it to the next person
> who replies to decide whether to continue this thread on that list
> rather than gcc@
>
> I only have to look as far as this to see a major problem:
> FAIL: 17_intro/headers/c++200x/all.cc (test for excess errors)
> Excess errors:
> In file included from
> /usr/local/src/trunk/gcc/libstdc++-v3/testsuite/17_intro/headers/c++200x/all.cc:111:
> /usr/local/src/trunk/objdir/sparc64-unknown-linux-gnu/64/libstdc++-v3/include/memory:86:48:
> error: tr1_impl/boost_sp_counted_base.h: No such file or directory
>
> That should not happen on any platform!
>
> And later:
> FAIL: 17_intro/using_namespace_std_tr1_neg.cc (test for excess errors)
> Excess errors:
> In file included from
> /usr/local/src/trunk/gcc/libstdc++-v3/testsuite/17_intro/using_namespace_std_tr1_neg.cc:40:
> /usr/local/src/trunk/objdir/sparc64-unknown-linux-gnu/64/libstdc++-v3/include/memory:86:48:
> error: tr1_impl/boost_sp_counted_base.h: No such file or directory
>
> Again, that should not happen on any platform.
>
> Thanks for the logs, I don't have any way to test on that platform
> unfortunately, but it seems that the symlinks for the new shared_ptr
> headers are missing.  I think that would happen if you hadn't done a
> clean bootstrap, since the Makefiles generated by configure would not
> have been updated when I added the new headers.
>
> Do you reuse objdir, without removing it entirely?

I have... I have also started e clean new build and check.

-- 
Cheers,

/ChJ

Reply via email to