I fixed my immediate problem by using a different version of gcc. Chris Lattner kirjoitti:> The offending line of code looks fine on our side, > but there could be something I'm missing.For what it is worth, I've run into problems with boost_concept_check before when using Boost.Python. Some versions of gcc worked fine, while others gave error messages relating to boost_concept_check. My guess is that it is due to some slight differences in how templates are instantiated in different versions of gcc. -- Pertti
On Wed, 2006-09-06 at 10:22 -0700, Chris Lattner wrote:> Okay. Question: does GCC 4.1.2 (if it exists) or GCC mainline fix the > problem? If so, we should document 4.1.1 as being buggy.FWIW, I returned to 3.4.6 when 4.1.1 didn't work out for me. I haven't tried 4.1.2. I'm waiting for the dust to settle on 4.2 Reid
On Wed, 6 Sep 2006, [ISO-8859-1] Pertti Kellom�ki wrote:> I fixed my immediate problem by using a different version > of gcc.ok.> Chris Lattner kirjoitti: >> The offending line of code looks fine on our side, >> but there could be something I'm missing. > > For what it is worth, I've run into problems with boost_concept_check > before when using Boost.Python. Some versions of gcc worked fine, > while others gave error messages relating to boost_concept_check. > My guess is that it is due to some slight differences in how templates > are instantiated in different versions of gcc.Okay. Question: does GCC 4.1.2 (if it exists) or GCC mainline fix the problem? If so, we should document 4.1.1 as being buggy. -Chris -- http://nondot.org/sabre/ http://llvm.org/
Chris Lattner kirjoitti:> Question: does GCC 4.1.2 (if it exists) or GCC mainline fix the > problem? If so, we should document 4.1.1 as being buggy.GCC 4.1.2 does not exist yet, but I grabbed the 4.2-20060906 snapshot of GCC and it compiled LLVM without problems. I verified that the hello world example from Getting Started worked, but did not test beyond that. This is on x86 Gentoo. -- Pertti