|
|
@ -128,6 +128,10 @@ $ make
|
|
|
|
|
|
|
|
|
|
|
|
This ran for 38 minutes -- I will not forget to run `make -j4` the next time :face_with_rolling_eyes:
|
|
|
|
This ran for 38 minutes -- I will not forget to run `make -j4` the next time :face_with_rolling_eyes:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< alert "circle-info" >}}
|
|
|
|
|
|
|
|
**Update**: This took <mark>3m 40s</mark> on my Raspberry Pi 4 2GB when run with `make -j4`.
|
|
|
|
|
|
|
|
{{< /alert >}}
|
|
|
|
|
|
|
|
|
|
|
|
You would now typically install the files but this is the part that made me stop for a while.
|
|
|
|
You would now typically install the files but this is the part that made me stop for a while.
|
|
|
|
|
|
|
|
|
|
|
|
~~~console
|
|
|
|
~~~console
|
|
|
@ -136,6 +140,10 @@ $ sudo make install
|
|
|
|
|
|
|
|
|
|
|
|
It will break, but at least it installs the binary files into `/usr/local/bin`.
|
|
|
|
It will break, but at least it installs the binary files into `/usr/local/bin`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< alert "circle-info" >}}
|
|
|
|
|
|
|
|
**Update**: I did not have these problems on the Raspberry Pi 4 any more.
|
|
|
|
|
|
|
|
{{< /alert >}}
|
|
|
|
|
|
|
|
|
|
|
|
Whatever I was doing, it won't work automated. I'm not a developer, but to me this looks
|
|
|
|
Whatever I was doing, it won't work automated. I'm not a developer, but to me this looks
|
|
|
|
like as if `make -C` enters the directory before it runs the top-level Makefile so the
|
|
|
|
like as if `make -C` enters the directory before it runs the top-level Makefile so the
|
|
|
|
`export ...` lines never get executed and the Makefiles in the sub-directories will never
|
|
|
|
`export ...` lines never get executed and the Makefiles in the sub-directories will never
|
|
|
@ -157,6 +165,11 @@ $ sudo make newhostfiles
|
|
|
|
|
|
|
|
|
|
|
|
Copy the systemd unit files to the right directory per hand:
|
|
|
|
Copy the systemd unit files to the right directory per hand:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< alert "circle-info" >}}
|
|
|
|
|
|
|
|
**Update**: Again, on the Pi 4 this was not needed. It looks like I messed something
|
|
|
|
|
|
|
|
up on the Raspberry Pi 2. Yet I leave the hints, they may become useful hopefully.
|
|
|
|
|
|
|
|
{{< /alert >}}
|
|
|
|
|
|
|
|
|
|
|
|
~~~console
|
|
|
|
~~~console
|
|
|
|
$ sudo cp debian/* /usr/lib/systemd/system/
|
|
|
|
$ sudo cp debian/* /usr/lib/systemd/system/
|
|
|
|
~~~
|
|
|
|
~~~
|
|
|
@ -232,6 +245,17 @@ Enable the UART in `/boot/config.txt`:
|
|
|
|
enable_uart=1
|
|
|
|
enable_uart=1
|
|
|
|
~~~
|
|
|
|
~~~
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
{{< alert "circle-info" >}}
|
|
|
|
|
|
|
|
**Update**: On the Raspberry Pi 4 again, we would write something like
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
~~~ini
|
|
|
|
|
|
|
|
enable_uart=1
|
|
|
|
|
|
|
|
dtoverlay=disable-bt
|
|
|
|
|
|
|
|
~~~
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
But we should not need to disable the serial console `serial-getty@ttyAMA0.service`.
|
|
|
|
|
|
|
|
{{< /alert >}}
|
|
|
|
|
|
|
|
|
|
|
|
Add this near the top or after `[All]`.
|
|
|
|
Add this near the top or after `[All]`.
|
|
|
|
|
|
|
|
|
|
|
|
We need to disable the serial console because we need the UART at the GPIO pins
|
|
|
|
We need to disable the serial console because we need the UART at the GPIO pins
|
|
|
@ -243,8 +267,9 @@ Disable the serial console service:
|
|
|
|
$ sudo systemctl disable serial-getty@ttyAMA0.service
|
|
|
|
$ sudo systemctl disable serial-getty@ttyAMA0.service
|
|
|
|
~~~
|
|
|
|
~~~
|
|
|
|
|
|
|
|
|
|
|
|
Open `/boot/cmdline.txt` and remove `console=serial0,115200` from the line. Save
|
|
|
|
Open `/boot/cmdline.txt` and remove `console=serial0,115200` from the line.
|
|
|
|
and reboot.
|
|
|
|
|
|
|
|
|
|
|
|
Save and reboot.
|
|
|
|
|
|
|
|
|
|
|
|
## Configuration
|
|
|
|
## Configuration
|
|
|
|
|
|
|
|
|
|
|
|