New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bin/menuconfig
to configure kernels
#109
Conversation
3fb4f90
to
af37a00
Compare
This wasn't a trivial thing to figure out.
With those combined, The fix I have started working on will be continued tomorrow. Though I'm not sure if the blame lies entirely within ncurses' court. As nothing else within Nixpkgs broke, I think the issue lies within how the kernel links applications. Still looking into it. |
Important, otherwise we lose additional options that may have been patched-in!
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.
This does present the drawback of not validating the kernel builds. Though I expect the user will build the kernel anyway after.
af37a00
to
c3d1ece
Compare
I can't reproduce this anymore :/. |
Hello @samueldr, Is there any workaround for now? Thanks Ref. log:
|
I assume this is a new failure coming from the recent changes in |
Had an epiphany about ways to co-opt the binary from out of a source tree.
TODO
asus-dumo
) it fails find ncurses through pkgconfig.Fixes #108