[retronet] Looking for a Raspberry Pi owner to help with bleeding edge testing.

[Cornelius Keck]

Got it to compile. Started out with instructions taken for Ubuntu and 
Debian, found on 
https://www.wireguard.com/install/#compiling-from-source. First step:

sudo apt-get install libmnl-dev libelf-dev linux-headers-$(uname -r) 
build-essential pkg-config

fails, because my Pi of choice runs 4.14.70+, and there is no 
linux-headers-... for it. Available headers (as of this afternoon) are:


pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910 $ sudo apt list 
--all-versions | grep -i linux-headers

WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.

linux-headers-3.10-3-all/stable 3.10.11-1+rpi7 armhf
linux-headers-3.10-3-all-armhf/stable 3.10.11-1+rpi7 armhf
linux-headers-3.10-3-common/stable 3.10.11-1+rpi7 armhf
linux-headers-3.10-3-rpi/stable 3.10.11-1+rpi7 armhf
linux-headers-3.16.0-4-all/stable 3.16.7-ckt4-1+rpi1+b2 armhf
linux-headers-3.16.0-4-all-armhf/stable 3.16.7-ckt4-1+rpi1+b2 armhf
linux-headers-3.16.0-4-common/stable 3.16.7-ckt4-1+rpi1+b2 armhf
linux-headers-3.16.0-4-rpi/stable 3.16.7-ckt4-1+rpi1+b2 armhf
linux-headers-3.18.0-trunk-all/stable 3.18.5-1~exp1+rpi19+stretch armhf
linux-headers-3.18.0-trunk-all-armhf/stable 3.18.5-1~exp1+rpi19+stretch 
armhf
linux-headers-3.18.0-trunk-common/stable 3.18.5-1~exp1+rpi19+stretch armhf
linux-headers-3.18.0-trunk-rpi/stable 3.18.5-1~exp1+rpi19+stretch armhf
linux-headers-3.18.0-trunk-rpi2/stable 3.18.5-1~exp1+rpi19+stretch armhf
linux-headers-3.6-trunk-all/stable 3.6.9-1~experimental.1+rpi7 armhf
linux-headers-3.6-trunk-all-armhf/stable 3.6.9-1~experimental.1+rpi7 armhf
linux-headers-3.6-trunk-common/stable 3.6.9-1~experimental.1+rpi7 armhf
linux-headers-3.6-trunk-rpi/stable 3.6.9-1~experimental.1+rpi7 armhf
linux-headers-4.4.0-1-all/stable 4.4.6-1+rpi14 armhf
linux-headers-4.4.0-1-all-armhf/stable 4.4.6-1+rpi14 armhf
linux-headers-4.4.0-1-common/stable 4.4.6-1+rpi14 armhf
linux-headers-4.4.0-1-rpi/stable 4.4.6-1+rpi14 armhf
linux-headers-4.4.0-1-rpi2/stable 4.4.6-1+rpi14 armhf
linux-headers-4.9.0-6-all/stable 4.9.82-1+deb9u3+rpi1 armhf
linux-headers-4.9.0-6-all-armhf/stable 4.9.82-1+deb9u3+rpi1 armhf
linux-headers-4.9.0-6-common/stable,now 4.9.82-1+deb9u3+rpi1 all 
[installed,automatic]
linux-headers-4.9.0-6-common-rt/stable 4.9.82-1+deb9u3+rpi1 all
linux-headers-4.9.0-6-rpi/stable,now 4.9.82-1+deb9u3+rpi1 armhf 
[installed,automatic]
linux-headers-4.9.0-6-rpi2/stable 4.9.82-1+deb9u3+rpi1 armhf
linux-headers-rpi/stable,now 4.9+80+deb9u4+rpi1 armhf [installed]
linux-headers-rpi-rpfv/stable 4.9+80+deb9u4+rpi1 armhf
linux-headers-rpi2/stable 4.9+80+deb9u4+rpi1 armhf
linux-headers-rpi2-rpfv/stable 4.9+80+deb9u4+rpi1 armhf
pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910 $

linux-headers-rpi sounds pretty good, so we'll run with that. Make fails:

pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910/src $ make
make[1]: *** /lib/modules/4.14.70+/build: No such file or directory.  Stop.
Makefile:36: recipe for target 'module' failed
make: *** [module] Error 2
pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910/src $

There is a build tool for an older kernel:

pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910/src $ ls -ls 
/lib/modules/*/build
0 lrwxrwxrwx 1 root root 34 Mar 31 09:43 /lib/modules/4.9.0-6-rpi/build 
-> /usr/src/linux-headers-4.9.0-6-rpi
pi at rpi004w:~/WireGuard/WireGuard-0.0.20180910/src $

Modifying Makefile to change this:

KERNELDIR ?= /lib/modules/$(shell uname -r)/build

to

KERNELDIR ?= /lib/modules/4.9.0-6-rpi/build

gets us a build. On a 0W it takes some time, but we do end up with a wg 
binary.

To be continued.



Grant Taylor via retronet wrote:
> On 09/18/2018 10:19 PM, Cornelius Keck via retronet wrote:
>> Got distracted, found an old disk drive with some good stuff on it
>> (not RPI-related, but old pix, plus what looks like a complete Maemo
>> development ‎environment for a Nokia 810). Problem is that the drive
>> is on the flaky side, doesn't always spin up, and it it does, the it
>> doesn't always shoe up on the bus. Of course reliable new drives
>> (HGST!!) are nowhere to be found close by, once that drive came
>> online. At this clip I might just put one new in the box up on the shelf.
>
> I *TOTALLY* understand.  I'm guilty of similar myself.
>
>> No worries, have not forgotten', just got into a priority override.
>
> Cool.  Thank you for friendly pong.
>
>
>
>
>
> _______________________________________________
> retronet mailing list
> retronet at mailman.chivanet.org
> http://mailman.chivanet.org/listinfo/retronet
>