libffi, missing symbolic link

Riccardo Mottola rmottola at opencsw.org
Sun Feb 16 12:10:43 CET 2014


Hi,


I had some success getting GNUstep work on solaris 8 & 10! however, when 
I updated right now on solaris 10, I cannot configure it anymore (use 
the same options though)

configure:13270: checking whether objc really works
configure:13300: gcc -o conftest -g -O2 
-I/opt/GNUstep/Local/Library/Headers 
-I/opt/GNUstep/Local/Library/Headers -I/o
pt/GNUstep/System/Library/Headers  -fgnu-runtime -x objective-c 
-L/opt/GNUstep/Local/Library/Libraries -L/opt/GNUstep/
Local/Library/Libraries -L/opt/GNUstep/System/Library/Libraries 
conftest.c -lrt -ldl  -lpthread -L/opt/csw/lib -R/opt/c
sw/lib -shared-libgcc -pthread -fexceptions -fgnu-runtime 
-L/home/multix/GNUstep/Library/Libraries -L/opt/GNUstep/Local
/Library/Libraries -L/opt/GNUstep/System/Library/Libraries 
-L/opt/GNUstep/Local/Library/Libraries -L/opt/GNUstep/Local/
Library/Libraries -L/opt/GNUstep/System/Library/Libraries -L/opt/csw/lib 
-lobjc -lxslt -L/usr/lib -R/usr/lib -lxml2 -lz
  -lpthread -lm -lsocket -lnsl -liconv -lffi -lnsl -lrt -ldl -lpthread 
-lz -licui18n -licuuc -licudata -lsocket -lnsl -l
m     >&5
In file included from ./config/config.objc.m:2:0,
                  from conftest.c:100:
./config/objc-common.g:30:1: warning: cannot find interface declaration 
for 'NXConstantString' [enabled by default]
  - (const char*) cString
  ^
ld: fatal: library -lffi: not found
ld: fatal: file processing errors. No output written to conftest

I then check for libffi and see:
  bash-4.2$ ls -l /opt/csw/lib/libffi*
lrwxrwxrwx   1 root     root          15 Dec 29 16:39 
/opt/csw/lib/libffi.so.4 -> libffi.so.4.0.1
-rwxr-xr-x   1 root     bin        50156 Sep 27 17:33 
/opt/csw/lib/libffi.so.4.0.1
lrwxrwxrwx   1 root     root          16 Apr  7  2013 
/opt/csw/lib/libffi.so.5 -> libffi.so.5.0.10
-rwxr-xr-x   1 root     bin        25000 Jun 25  2011 
/opt/csw/lib/libffi.so.5.0.10

I see that there is no main .so library linked to, I'd expect, so.5

I suppose this is an upgrade/package problem? what's your take?
(it would be even better to upgrade all packages to one libffi version, 
in my experience, but that's a different thing)

Riccardo


More information about the devel mailing list