This commit adds the wireguard module patch through the
wireguard-linux-compat repo. This also adds the wireguard-tools, the
userspace tool for wireguard
Signed-off-by: Sayan Chowdhury <sayan@kinvolk.io>
The BINHOST was still configured to be the CoreOS CL upstream location
which does not work for independent Flatcar CL releases. This broke
binary package installation in the development container.
Use the correct BINHOST to fix installation of binary packages in the
development container.
The user can only login via SSH if no password was set and can't login
over the serial console in the web UI. To login, the user needs to press
reboot and then append flatcar.autologin to the kernel command line parameters
in GRUB each time. The user may also not know that this option even exists.
Set flatcar.autologin by default in the kernel command line parameters for
Azure so that users don't need to set this themselves.
`dev-lang/rust` has been moved to coreos-overlay since a long time.
However, we have still kept `dev-lang/rust` in portage-stable as well.
As it is not needed at all, let's simply remove it.
Since strace 5.3 or newer is not enabled for `amd64` and `arm64` by
default, we need to add keywords `~amd64` and `~arm64` for newer
versions of strace.
Update strace to 5.6, to make it compatible with recent Kernels.
It does not include a third-party patch `strace-5.5-static.patch`,
which could cause build failures with pkgconfig <= 2.28.
We updated `virtual/rust` to 1.41.1, but have not done so for
`dev-lang/rust`, which remains as 1.36.0. Such a mismatch prevents
the whole build to fail.
For now, let's revert `virtual/rust` back to 1.36.0.
Since `virtual/cargo` does not exist in the recent Rust ebuilds,
dependency on the missing package `virtual/cargo` caused build issues
in the SDK. So we should make it depend on `virtual/rust` to fix the
build issues.
Now that `cross-{x86_64,aarch64}-cros-linux-gnu/gdb` was updated to 9.1,
it needs exactly one of `python_single_target_python3_6` and
`python_single_target_python3_7`. Since python 3.7 is not available yet,
we need to enable 3.6 and disable 3.7, for the SDK profile.
Without the fix, toolchain builds will fail like that:
```
!!! The ebuild selected to satisfy "cross-aarch64-cros-linux-gnu/gdb"
has unmet requirements.
- cross-aarch64-cros-linux-gnu/gdb-9.1-r1::x-crossdev USE="client nls python server -lzma -multitarget -source-highlight -test -vanilla -xml -xxhash"
PYTHON_SINGLE_TARGET="-python3_6 (-python3_7)" PYTHON_TARGETS="python3_6 (-python3_7)"
The following REQUIRED_USE flag constraints are unsatisfied:
python? ( exactly-one-of ( python_single_target_python3_6 python_single_target_python3_7 ) )
The above constraints are a subset of the following complete expression:
python? ( exactly-one-of ( python_single_target_python3_6 python_single_target_python3_7 )
python_single_target_python3_6? ( python_targets_python3_6)
python_single_target_python3_7? ( python_targets_python3_7 ) ) any-of ( client server )
```
The configuration variables for the Ignition configuration also serve as
data source for coreos-cloudinit config data (which includes plain scripts).
Document them properly and also call out that the networking variables only
work if coreos-cloudinit data is used.
For some use cases, too few networking variables were available. Add secondary
routing variables for the main network interface and add a second interface.
The user can only login via SSH if no password was set and can't login
over the VGA console in the web UI. To login the user needs to press
reboot and then append flatcar.autologin to the kernel command line parameters
in GRUB each time. The user may also not know that this option even exists.
Set flatcar.autologin by default in the kernel command line parameters for
VMware so that users don't need to set this themselves.
Update gdb to 9.1, and add --without-libmpfr-prefix to configure.
Since we should remove gdb from portage-stable, we need to update gdb
to 9.1 in coreos-overlay.
