Re: Error using libffi with g++-mp-4.7

[Anthony Green <green at moxielogic dot com>]

On 2/25/2012 2:24 PM, Murilo Adriano Vasconcelos wrote:
> I'm trying to use the libffi with g++-mp-4.7 compiler and I'm getting
> an error because of an #elif without expression.
> Here is the description of my compiler:
>
> murilo@mac:my_clever$ g++-mp-4.7 -v
> Using built-in specs.
> COLLECT_GCC=g++-mp-4.7
> COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin10/4.7.0/lto-wrapper
> Target: x86_64-apple-darwin10
> Configured with: ../gcc-4.7-20111203/configure --prefix=/opt/local
> --build=x86_64-apple-darwin10 --enable-languages=c,c++,objc,obj-c++
> --libdir=/opt/local/lib/gcc47 --includedir=/opt/local/include/gcc47
> --infodir=/opt/local/share/info --mandir=/opt/local/share/man
> --datarootdir=/opt/local/share/gcc-4.7 --with-local-prefix=/opt/local
> --with-system-zlib --disable-nls --program-suffix=-mp-4.7
> --with-gxx-include-dir=/opt/local/include/gcc47/c++/
> --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local
> --enable-stage1-checking --disable-multilib
> Thread model: posix
> gcc version 4.7.0 20111203 (experimental) (GCC)
>
> In fact there is an #elif without expression in my ffi.h on line 298:
>
> #elif
> #error FFI_CLOSURES not defined
> #endif
>
> I believe that changing that #elif to an #else would fix this issue.

Yes, no doubt it would.  However, I think that you're looking at some 
old fork of libffi.  Google search tells me that some version of PyOBJC 
contains a libffi derivative with that code.  Where did you get your 
libffi source from?

Can you try http://github.com/atgreen/libffi ?

AG



> Regards,
> --
> Murilo Adriano Vasconcelos
> http://clever-lang.github.com/
> http://murilo.wordpress.com