Cjdns fails to build on Raspberry Pi 2

[Shnatsel]

It appears to be failing on "Running test EncodingScheme_testTIMEOUT" and builds successfully with "NO_TEST=1".

Full build log: http://pastebin.ubuntu.com/13536784/

Tested on master from https://github.com/cjdelisle/cjdns/, RPi 2, Raspbian Jessie

[koalalorenzo]

Same problem for me! This is my output: http://pastebin.com/YmwZ2L9p

[koalalorenzo]

I still can't access, but apparently cjdns was compiled for ARMv7 and it is working with http://archlinuxarm.org/

Probably some dependencies are missing or some libraries are not updated.

[koalalorenzo]

I have been trying to build it using gcc 4.7, 4.8 and 4.9. on All of them it seems to fail for a timeout during testing. Still using Raspbian Jessie.

I have also tried with "./cross-do", it compiles but it is not able to connect returning this error: http://pastebin.com/akKwNJtp

I really would like to understand how to get cjdns on Raspbian Jessie, for Raspberry Pi 2 (ARMv7) since other distribution were able to. Nobody seems to care.

[koalalorenzo]

It seems to be related to #6

[Shnatsel]

NO_TEST=1 Seccomp_NO=1 ./do

this works as a temporary workaround for both this issue and #6

[Kubuxu]

Can someone of you show result of

sudo zcat /proc/config.gz | grep CONFIG_SECCOMP_FILTER

and also uname -a.

[Shnatsel]

$ sudo zcat /proc/config.gz
gzip: /proc/config.gz: No such file or directory

$ uname -a
Linux raspberrypi 4.1.12-v7+ #824 SMP PREEMPT Wed Oct 28 16:46:35 GMT 2015 armv7l GNU/Linux

If you find any way to get the kernel config on Raspberry Pi please let me know, because we also need it for #6

[Kubuxu]

It might be also in /boot/. If not then manual kernel compilation guide.

[Kubuxu]

Here is the config: https://github.com/raspberrypi/linux/blob/rpi-4.1.y/arch/arm/configs/bcm2709_defconfig

There is CONFIG_SECCOMP=y but no CONFIG_SECCOMP_FILTER=y which might be a cose a problem.

[Shnatsel]

There is /boot/config.txt but it's not kernel configuration, it's this: https://ncry.pt/p/YpBn#HpPNrZgtWJm-cTL4rc1jFmGDY1_UcfPPtUSnP7mVFq8

[Kubuxu]

It is duplicate of #6 it should be closed on a benefit of older issue.

[Shnatsel]

No. #6 is about SECCOMP failing, this is about a timed test failing. It still fails if I disable SECCOMP but leave tests enabled.

[Shnatsel]

Build still fails with ./clean Seccomp_NO=1 ./do, so this is NOT a dupe of #6 after all.

[koalalorenzo]

So, It will compile and it seems to work correctly (even the tests) by running Seccomp_NO=1 ./do

I will probably take care of another guide, suggesting to recompile the kernel to enble the feature.

[koalalorenzo]

I agree with @Kubuxu we should probably close this and report in the other Issue

[Kubuxu]

Copy of #6.