The problem is that silc-client uses yasm to compile some amd64 assembly, but specifies the object type as "elf". Yasm (or at least yasm-0.6.0) interprets "elf" to mean "elf32", and obviously that doesn't too great work on amd64: /bin/sh ../../libtool --tag=CC --mode=compile /usr/bin/yasm -Xgnu -felf aes_x86_64.asm /usr/bin/yasm -Xgnu -felf aes_x86_64.asm -o aes_x86_64.o aes_x86_64.asm:693: warning: `rsp' is a register in 64-bit mode aes_x86_64.asm:693: undefined symbol `rsp' (first use) aes_x86_64.asm:693: (Each undefined symbol is reported only once.) aes_x86_64.asm:694: warning: `rsp' is a register in 64-bit mode aes_x86_64.asm:694: warning: `rsi' is a register in 64-bit mode [...] aes_x86_64.asm:856: warning: `rsp' is a register in 64-bit mode make[3]: *** [aes_x86_64.lo] Error 1 make[3]: Leaving directory `/var/tmp/portage/net-im/silc-client-1.1.2/work/silc-client-1.1.2/lib/silccrypt' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/net-im/silc-client-1.1.2/work/silc-client-1.1.2/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/net-im/silc-client-1.1.2/work/silc-client-1.1.2' make: *** [all] Error 2
Created attachment 125148 [details] fixed silc-client-1.1.2.ebuild Solution is to sed configure and replace felf with felf64 on amd64.
Hrm...why it uses yasm?
(In reply to comment #2) > Hrm...why it uses yasm? For fast crypto.
But how does that work? Just having yasm installed? I'm asking because i was able to built it successfully on amd64, but i don't have yasm installed.
(In reply to comment #4) > But how does that work? Just having yasm installed? I'm asking because i was > able to built it successfully on amd64, but i don't have yasm installed. Have a look at configure.ac, it automatically looks for nasm and yasm, and uses them if they are available. Convenient.
Shrug...stupid build system...okay, i'll have a look, thanks for the info
Fixed, thanks.
