| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
targetPlatform is the platform the current package's programs will
produce binaries for — only relevant for compilers and
similar. hostPlatform is the platform the current package's programs
will run on.
The incorrect use of targetPlatform meant that anything that tried to
link to it (like cryptsetup) would fail to build when it was used as a
native build input for a cross-compiled Musl derivation.
|
| |
|
|
| |
Reduces the closure size of pkgsStatic.kmod from 51.0M to 541.6K.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generate-config.pl's auto modules feature answers "m" to any Kconfig
question it thinks supports being a module. It detected this by
seeing if the help shown by make config (called "alts" by the script)
contained the string "/m", which it would in the case of e.g a
tristate option, where alts would be "N/m/y/?".
But then along came CONFIG_MODPROBE_PATH in Linux 5.13, with a default
value, shown in the make config help, of "/sbin/modprobe".
generate-config.pl would see the "/m" substring, and answer "m" to the
question, meaning (I think) that the built kernel would expect the
modprobe binary to be at /m. This broke the (non-NixOS) VM images I
build with Nix. NixOS was unaffected because it uses a different
mechanism to set the modprobe path.
With the current architecture, we can't 100% determine whether a
Kconfig option is a string or a tristate, but we can get a lot closer
by using a better regex. My new regex only accepts single word
characters, separated by slashes, with a "/?" at the end. This is
much less likely to ever end up as the default value of a string
option.
Tested by building linux_latest.configfile before and after my
changes, and checking the only difference is the correct default for
CONFIG_MODPROBE_PATH.
|
| |
|
|
|
|
|
|
| |
Some use cases (think appliances) call for veritysetup but not
cryptsetup, and others (like NixOS) don't need veritysetup and usually
not integritysetup. This is especially useful for pkgsStatic where
each program contains a whole copy of the libraries it needs so is
quite large.
|
| |
|
|
|
|
|
|
|
|
|
| |
This reduces closure sizes by making the libraries not depend on the
binaries, which is good for static builds, and (when statically
linked) making the binaries not depend on the libraries, which is good
for static builds.
When static building, we additionally have to disable loading LUKS
plugins from $lib to avoid a reference, which probably wouldn't have
worked anyway.
|
| | |
|
| |
|
|
|
| |
I think "CLI" is a very strange name for this, but that's what
upstream calls it.
|
| | |
|
| |
|
|
| |
Fixes the build with Linux 5.17.
|
| |
|
|
| |
smem 1.5 has support for python3
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
When something changes in nixos-rebuild, we must make sure the
installers still work, otherwise it might break existing setups.
The installer tests check whether nixos-rebuild works, so they are a
good lithmus test.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nixos-rebuild would forward all verbose flags to nix, but not actually
increase its own verbosity.
Which would make it hard to see what’s going on without resorting to
tools like strace or adding `set -x` to the script.
We add a simple exec wrapper around the most “interesting” commands,
that is nix tool invocations. If any verbosity flag is given, it will
set the verbosity flag of the nixos-rebuild script all commands
wrapped into `runCmd` will start logging their invocation.
This is done via a `logVerbose` function, which can also be used to
print logging messages when in verbose mode, to aid debugging why
nixos-rebuild does what it does. A few messages are added, but
potentially we could log a lot more details.
Now, testing all of the changed code paths turns out to be rather
hard, so I am unsure how to verify that for all changed commands
behaviour stays indeed the same.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
To support this theoretically, the configure script upstream would need
to a) stop using PATH for finding python-config exclusively and allow
passing an absolute path to it and b) cease using the distutils module
for configuration purposes which of course requires running the host
python interpreter which is not possible in the cross case.
|
| |\ \
| | |
| | | |
usbguard: 1.1.0 -> 1.1.1
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| | |
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
|
| | |
| |
| | |
greter -> greeter
|
| |\ \
| | |
| | | |
udisks2: correct patch
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This was forgotten during https://github.com/NixOS/nixpkgs/pull/147606
|
| |\ \ \
| | | |
| | | | |
pacemaker: init
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflict in pkgs/development/libraries/libvirt/default.nix
required manual adjustments. The fetched patch is already in src.
I checked that libvirt builds.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
bcachefs: unstable-2022-01-12 -> unstable-2022-03-09
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
As requested in https://github.com/NixOS/nixpkgs/pull/163433#issuecomment-1066169644
|
| | | | | | | |
|
| |\| | | | | |
|
| | |\ \ \ \ \
| | |_|_|_|/
| |/| | | | |
Change metalab mirrors to ibiblioPubLinux ones
|
| | | | |_|/
| | |/| | |
|
| |\| | | | |
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
linuxPackages.*: various fixes related to cross compilation
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
nativeBuildInputs
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
nativeBuildInputs
|
| | | | | |
| | | | |
| | | | |
| | | | | |
nativeBuildInputs
|
| | | | | |
| | | | |
| | | | |
| | | | | |
nativeBuildInputs
|
| | | | | | |
|
| | | | | | |
|