On Fri, Jul 5, 2013 at 3:58 AM, Andrew Haley <aph@xxxxxxxxxx> wrote: > On 07/05/2013 08:53 AM, Jeffrey Walton wrote: >> On Thu, Jul 4, 2013 at 6:34 AM, Andrew Haley <aph@xxxxxxxxxx> wrote: >>> On 07/04/2013 11:07 AM, Jeffrey Walton wrote: >>>> What can I do to try and isolate the problem? >>> >>> The problem is obvious: all those macros expand to some truly >>> ridiculous code. You can see this with "g++ -E" >> >> The odd thing is, other compilers (GCC, ICC/ICPC, Clang, and MSVC) can >> compile the file. I only have the problem with Apple's gcc/g++, which >> is llvm-gcc. Once I switched to clang/clang++, the problem went away. > > Sure, but that's a political problem: you'd have to find someone who > wants to work on Apple's GCC. Absolutely. I pretty sure its abandoned and was hoping to find a work around. To try and find a work around, I needed to identify the problem (thanks again, BTW). Jeff
