Is nng compiled as a shared library? Because it looks like it’s linking against 
an archive file.

> On Oct 14, 2021, at 20:49, Matt Welland <mattrwell...@gmail.com> wrote:
> 
> 
> I added "-C" "-fPIC" and get this:
> 
> matt@mars:~/src/chicken-nng$ ck5 chicken-install -s
> building nng
>    /home/matt/data/buildall/ck5.2/bin/csc -host -D compiling-extension -J -s 
> -regenerate-import-libraries -setup-mode -I /home/matt/src/chicken-nng -C 
> -I/home/matt/src/chicken-nng -C -fPIC -L -lnng src/nng.scm -o 
> /home/matt/src/chicken-nng/nng.so
> /usr/bin/ld: //usr/local/lib/libnng.a(nng.c.o): relocation R_X86_64_PC32 
> against symbol `nng_recvmsg' can not be used when making a shared object; 
> recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status
> 
> Error: shell command terminated with non-zero exit status 256: 'gcc' 
> '/home/matt/src/chicken-nng/nng.o' -o '/home/matt/src/chicken-nng/nng.so' 
> -shared -lnng -L/home/matt/data/buildall/ck5.2/lib 
> -Wl,-R/home/matt/data/buildall/ck5.2/lib -lchicken -lm -ldl
> 
> Error: shell command terminated with nonzero exit code
> 256
> "sh /home/matt/src/chicken-nng/nng.build.sh"
> 
> I'm wondering if my nng install is somehow broken? I compiled and ran the 
> reqrep demo and it works fine.
> 
>> On Wed, Oct 13, 2021 at 4:22 PM Ariela Wenner <aris...@disroot.org> wrote:
>> 
>> Huh, weird. I have been trying to replicate whatever is going on, without 
>> luck
>> so far.
>> 
>> Would you mind editing the csc-options inside the egg definition on line 8?
>> 
>> Should look like this:
>> 
>> (csc-options "-C" "-fPIC" "-L" "-lnng")
>> 
>> Then try building again. If the error persist send me the logs and I'll look
>> into it.
>> 
>> Cheers!
>> 
>> On Wed, 13 Oct 2021 16:00:46 -0400
>> Matt Welland <mattrwell...@gmail.com> wrote:
>> 
>> > OS is lubuntu 20.04, latest nng from git.
>> > 
>> > Thanks.
>> > 
> 
> 
> -- 
> --
> Complexity is your enemy. Any fool can make something complicated.
> It is hard to keep things simple. - Richard Branson.

Reply via email to