gnustep-base configure failure on x86

Riccardo Mottola rmottola at opencsw.org
Wed Mar 4 00:19:29 CET 2015


Laurent Blume wrote:
> Le 2015/03/03 21:05 +0100, Riccardo Mottola a écrit:
>
> cc config.ffi.c -L/opt/csw/lib/ffi -R/opt/csw/lib/ffi -lffi
> -I/opt/csw/include
>
> When did GCC acquire that feature??
>
>
> On the problem, it's definitely libffi.so.5 hich is broken. Building
> with .4, it works:
>
> $ gcc config.ffi.c /opt/csw/lib/libffi.so.4
> $ ./a.out
> $ echo $?
> 0
yes, I tried that too.. so.4 works so.5 not

>
> Considering the libffi recipe is still using the default obsolete
> compiler, I can only advise to give it a try with SOS12U4, then with Gcc4.
>
> You have a fair use of LD_LIBRARY_PATH there: point it to your newly
> built lib so a.out picks it up (check with ldd) and you can try it
> quickly without having to install it.
So I should try to build locally a package and then point to it? Ok
But how can I select different compilers?

I see also the receipe forces 64biit, is that correct?

$file a.out
a.out:          ELF 32-bit LSB executable 80386 Version 1, dynamically 
linked, not stripped, no debugging information available

while the two libffi's appare slighlty different:

/opt/csw/lib/libffi.so.4:       ELF 32-bit LSB dynamic lib 80386 Version 
1, dynamically linked, not stripped
/opt/csw/lib/libffi.so.5:       ELF 32-bit LSB dynamic lib 80386 Version 
1 [FPU], dynamically linked, not stripped

also:
dd /opt/csw/lib/libffi.so.4
         libgcc_s.so.1 =>         /opt/csw/lib/i386/libgcc_s.so.1
         libc.so.1 =>     /lib/libc.so.1
         libm.so.2 =>     /lib/libm.so.2

ldd /opt/csw/lib/libffi.so.5
         libc.so.1 =>     /lib/libc.so.1
         libm.so.2 =>     /lib/libm.so.2


Riccardo


More information about the maintainers mailing list