Usage in NixOS #2
Comments
|
Hi! I'm very humbled that you'd attempt to use autokernel for the NixOS build process. Sorry for the inconveniences, the integration tests are currently a little rough around the edges. The tests are currently assuming the existence of some system utilities, so there are some useless error messages produced if something mandatory isn't found. I created this tool just before I switched to NixOS myself, so there are some dependencies left that are not properly documented right now. (I didn't notice them on gentoo previously for obvious reasons) About your issue: You are encountering the Generally I tried to derive all required tools for building the kernel from the upstream definition here and arrived at the following commands: > nix shell nixpkgs#{gcc,bash,gnumake,perl,gmp,libmpc,mpfr,bison,flex,pahole,python3,wget,tar}
> ln -s /nix/store/...bash-5.2-p15/bin/bash /bin/bash # Very hacky, sorry :(
> cargo test --test integration_tests -- --nocapture integration_setup
Finished test [unoptimized + debuginfo] target(s) in 0.10s
Running tests/integration_tests.rs (target/debug/deps/integration_tests-84e17e38762193f8)
running 1 test
creating /tmp/autokernel-test directory
kernel tar already in cache
extracting kernel linux-5.19.1 ...
Built bridge for /tmp/autokernel-test/linux-5.19.1 in 6.34s
Initialized bridge [kernel 5.19.1, 16885 symbols] in 2.30s
test integration_setup ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 3 filtered out; finished in 16.46s(wget and tar are required for the integration test, but it seems like you have those already. Also /tmp must allow executable files at the moment, not sure whether that might become a problem in NixOS build sandbox) I guess I should probably switch to a flake based build for this project to avoid the issues, but I'm not yet entirely sure what the best way would be to do that. I hope this solves your issue, if you need additional information for your integration attempt I'm of course glad to help! |
|
Ah, you want that shebang to be Also, if you are interested, I'm working on the new kernel build infrastructure here: /~https://github.com/lovesegfault/nixpkgs-kernel-redux The idea is to translate a Nix module into an autokernel config, and then use that to generate the final config file. You can see that being done here: /~https://github.com/lovesegfault/nixpkgs-kernel-redux/blob/main/kconfig/default.nix One thing that |
|
(I'll submit a PR packaging this with a flake, I already did most of the work here: /~https://github.com/lovesegfault/nixpkgs-kernel-redux/blob/main/kconfig/autokernel.nix) |
True, that's probably a better way to do it. Do you know what nixos is doing to make the kernel scripts work? AFAIK those all start with
Awesome, thanks for the links!
Yep, currently autokernel just accepts a path without any logic behind it like: load_kconfig_unchecked(kernel_dir .. "/arch/x86/configs/x86_64_defconfig")I didn't want to put special logic into autokernel itself to figure out the correct path, since it's not directly obvious what it would be and if it would change in the future. Just have a quick look at the following examples: Since autokernel has access to the build-time environment variables, we can derive the location automatically: In the Makefile it is defined as load_kconfig_unchecked(kernel_dir .. "/arch/" .. ak.kernel_env("SRCARCH") .. "/configs/" .. ak.kernel_env("KBUILD_DEFCONFIG"))Does that solve your problem? On a related note: How do you feel about using lua to do the config? For other distributions I felt this is a good compromise between being easy to read and configure while still having access to more powerful functionality, but for nix I'm not entirely sure whether lua is the best language for the job. The whole scripting system is already entirely decoupled from autokernel's main functionality, so if you have an idea for a better config format / language it wouldn't be too much work to get that in. |
|
We could use /~https://github.com/nix-community/patsh for patching the shell stuff, it's already used in a few other nipxkgs. |
Hi!
I'm working on a new approach to kernel builds for the NixOS project and wanted to try using autokernel, but have been struggling to make it work.
Firstly, I cannot get the integration tests to pass:
This same problem is reflected when I try to use autokernel for our kernel builds, which fail:
The text was updated successfully, but these errors were encountered: