The applet is specifically written to show what we call the "recovery
menu". Yes, it's also the boot selection, but it will get confusing with
the upcoming boot tracking splash UI that's upcoming.
It looks like this is not a regression from the latest changes to the
kernel builder. Testing on top of ffdba8fecb
exhibits the same issue.
This change works around the issue by doing it with one invocation of
`make`, rather than doing it twice.
It has not been figured out at which exact version of the kernel this
stops being an issue, and if it is an issue from mainline Linux
outright, or something that came from Android-specific modifications.
Though it has been verified that for 3.18, both Qualcomm and Mediatek
source trees exhibit the same issue.
Fixes#216
This is a temporary measure. The last changes have proven that we can't
just overrideAttrs things willy-nilly like that, and that the whole
builder is in need of a revamp.
Let's wait for the revamp, and do the minimum work required to fix the
normalization for existing builds.
This uses the actual output expected by the build, rather than hoping
menuconfig gives the same result.
For kernels prior to 5.8 it wasn't an issue.
Starting with 5.8 the build environment will influence the actual
configuration used.
We're stripping some information when comparing.
The exact TEXT_VERSION string will change according to whether it's a
native or cross compilation.
Finally, minor version bumps are not relevant here.
This works around an issue with upstream Nixpkgs and the way pkg-config
is now (admitedly rightly so) prefixed.
In actuality, the kernel build should be fixed upstream, but this would
be a non-trivial thing to get into the kernel.
Bindings to libffi, with (approximatively) the same API as the Ruby
Fiddle stdlib.
This uses a fork with fixes, and hopefully improvements and
maintainership in the future.
While staying compatible with older ones.
These changes are required since recent kernels' nconfig expect that the
Makefile will have setup the environment for *many* things.
We can't simply run nconfig directly anymore.
What's that about `run-nconfig`?
Well, `make nconfig` tries to build again, in a situation where it won't
be able to build. *sigh*. With this, we take the assumedly-fine-to-run
nconfig that is already in our botched up source tree.
