missing libffi.so master link

[Dagobert Michelsen]

Hi Riccardo,

> Am 09.03.2015 um 08:59 schrieb Riccardo Mottola <rmottola at opencsw.org>:
> 
> Laurent Blume wrote:
>> Le 2015/03/08 21:00 +0100, Riccardo Mottola a écrit:
>>> This on unstable10x:
>>> libtool: link: /opt/csw/bin/gcc-4.9 -shared  -fPIC -DPIC -Wl,-z -Wl,text
>>> -Wl,-h -Wl,libffi.so.6 -o .libs/libffi.so.6.0.4 src/.libs/prep_cif.o
>>> src/.libs/types.o src/.libs/raw_api.o src/.libs/java_raw_api.o
>>> src/.libs/closures.o src/x86/.libs/ffi64.o src/x86/.libs/unix64.o
>>> src/x86/.libs/ffi.o src/x86/.libs/sysv.o -L/opt/csw/lib/64  -O2 -m64
>>> -march=opteron -m64 -march=opteron -m64 -march=opteron
>>> ld: fatal: file src/x86/.libs/unix64.o: section [5].eh_frame: section
>>> type is SHT_PROGBITS: expected SHT_AMD64_UNWIND
>>> collect2: error: ld returned 1 exit status
>>> Makefile:1165: recipe for target 'libffi.la' failed
>> 
>> Some search seems to hint it's a GNU assembler / Solaris ld issue. There might be some optimization selected by ./configure that's not good.
>> http://gcc.1065356.n5.nabble.com/Building-GCC-4-7-2-on-Solaris-10-x86-AMD64-Getting-linker-error-involving-eh-frame-td893484.html 
>> 
>> I see that option in configure that's probably worth enabling:
>> 
>> --enable-portable-binary
>> 
>> Check the config.log carefully.
>> 
> I enabled that option. I don't seeit mentioned in the thread you cite though.
> 
> I see this in the configure output.
> 
> pentium-pro run:
> checking whether .eh_frame section should be read-only... expr: syntax error
> no
> 
> amd64 run:
> checking toolchain supports unwind section type... no
> checking whether .eh_frame section should be read-only... expr: syntax error
> no
> 
> and it could be related, it is the same section. The check before is about unwind, apparently run on amd64 only.
> 
> in config.log I just see:
> configure:18550: checking toolchain supports unwind section type
> configure:18579: result: no
> configure:18589: checking whether .eh_frame section should be read-only
> configure:18609: result: no
> 
> no trace of the "expr" error and of the actual test.

Take a look in config.log, if in doubt add „set -e“ to configure and store the output.

>>> that is,  have trouble only on intel.. of which I don't know much. Help!
>> 
>> Solaris 9 x86 is 32 bit only. My generic advice about it is: drop it.
> 
> I'm fine for dropping x86, but I'd like tor retain solaris9 on sparc. May I or do I need to upload both packages together like it happens on solaris 10?

Please *always* provide x86 and sparc. Rule of thumb: dropping something altogether
is better than providing for one ISA only.

> seems like I became libffi maintainer :)

Welcome to the club :)


Best regards

  — Dago

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2418 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20150309/8183e766/attachment.p7s>