On 07/27/2012 02:17 AM, Mathieu Malaterre wrote: > On Fri, Jul 27, 2012 at 4:13 AM, Steve M. Robbins <st...@sumost.ca> wrote: >> Hey ... is there a trick to fix #654718 similar to that for __int128? > > #undef _GLIBCXX_USE_FLOAT128
No, that is not the same problem. The __int128 fix told the *standard library* headers not to use the type by setting its own preprocessor symbols correctly. In this case the problem is in the fftw headers. The fftw3.h header contains a big #if test to decide whether the __float128 type is available. It *already* contains an exclusion for the Intel compiler. It also needs an exclusion for gccxml just as it would for any other compiler that defines __GNUC__ but is not really the GNU compiler version it reports. This is what I suggested in the original thread on our list: http://thread.gmane.org/gmane.comp.compilers.gccxml/602 Other projects have accepted upstream modifications for the same reason, such as Boost: http://svn.boost.org/svn/boost/tags/release/Boost_1_50_0/boost/config/compiler/gcc_xml.hpp -Brad -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
