Re: [Boost-users] [uBLAS] Strange bug with nvcc

Subject: Re: [Boost-users] [uBLAS] Strange bug with nvcc
From: Lars Viklund (zao_at_[hidden])
Date: 2012-02-10 19:26:18

On Fri, Feb 10, 2012 at 02:57:54PM +0000, Chris Jewell wrote:
> /home/stats/stsiab/include/boost/numeric/ublas/vector_sparse.hpp:390: error: ‘__T13’ has not been declared
> 
> What is "__T13"?  grep on the Boost source doesn't find it, so I assume that I'm missing a header from somewhere else?  The other odd thing is that there is no reference to my CUDA file.  Furthermore, everything works well on my MacBook Pro with GCC 4.2.1 and nvcc 4.1.

When you get mysterious token errors appearing in source code, the
culprit is almost always a rogue macro defined by the compiler or by
some header earlier in the build process.

Look at the untainted source line, see what originally is there and look
for what could make it expand in a way you don't expect it to.

Single-letter macros tend to be more common than you think, it could be
as simple as a
#define M __T13
sneaking in from the toolchain you use.

-- 
Lars Viklund | zao_at_[hidden]