| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-08-01 | 3 | -0/+17 |
| |\ |
|
| | * | lib.systems: Add examples & helpers for MSVC | Ross Smyth | 2025-07-31 | 3 | -0/+17 |
| * | | Merge branch 'staging-next' into staging | Wolfgang Walther | 2025-07-24 | 4 | -517/+534 |
| |\| |
|
| | * | treewide: run nixfmt 1.0.0 | Wolfgang Walther | 2025-07-24 | 4 | -474/+491 |
| * | | nodejs: split destCPU into stdenv.$platform.node•••this architecture mapping is used broadly in the node ecosystem.
an assortment of tools and hooks, like buildNpmPackage or
pnpm.configHook, will benefit from reusing these values. placing them in
stdenv makes sense because (1) several of these tools don't currently
depend on nodejs, and may even be available where nodejs is not and (2)
`stdenv.{build,host,target}Platform` seems to be less error-prone than
`pkgs*.nodejs.{os,arch}` -- especially for setup hooks where the offsets
are shifted.
| Colin | 2025-07-07 | 1 | -0/+45 |
| |/ |
|
| * | lib.systems.examples: Add rust.rustcTarget for ppc64-elfv1 | OPNA2608 | 2025-07-05 | 1 | -0/+1 |
| * | lib.systems.inspect.patterns: init isAbiElfv1 | OPNA2608 | 2025-06-26 | 1 | -0/+5 |
| * | lib.systems.examples: Split glibc powerpc64 back into 2 ABI options•••ELFv1 is the historically better supported one on glibc, ELFv2 seems to have some issues with our toolchain.
Restore the option to pick the ABI with pkgsCross.
| OPNA2608 | 2025-06-21 | 1 | -1/+5 |
| * | lib.systems: don't throw if go unsupported•••Better to have a value that can actually be checked for, rather than
throwing, so optional Go support can be disabled when unsupported.
| Alyssa Ross | 2025-05-30 | 1 | -1/+1 |
| * | lib: prefer replaceString over replaceStrings | Gutyina Gergő | 2025-05-28 | 1 | -2/+2 |
| * | lib.systems.loongarch64-multiplatform: init | Weijia Wang | 2025-05-25 | 1 | -0/+11 |
| * | lib.systems: raise minimum loongarch64 feature support (#403201) | Aleksana | 2025-05-23 | 3 | -1/+69 |
| |\ |
|
| | * | lib.systems.examples: separate loongarch64 for desktop and embedded variants | aleksana | 2025-05-22 | 2 | -1/+24 |
| | * | lib.systems.architectures: add loongarch64 | aleksana | 2025-05-22 | 1 | -0/+45 |
| * | | lib.systems.elaborate.canExecute: handle different gcc.arch (#403549) | Aleksana | 2025-05-23 | 2 | -1/+79 |
| |\ \
| |/
|/| |
|
| | * | lib.systems.elaborate.canExecute: handle different gcc.arch | aleksana | 2025-05-22 | 1 | -1/+15 |
| | * | lib.systems.architectures: add hasInferior and canExecute function | aleksana | 2025-05-22 | 1 | -0/+64 |
| * | | lib.systems.examples.riscv64-musl: init | Alyssa Ross | 2025-05-15 | 1 | -0/+4 |
| * | | lib/systems: remove android cruft•••These used legacy names for Android SDK and NDK versions, so now we can
do away with them.
| Morgan Jones | 2025-05-12 | 1 | -15/+3 |
| * | | lib.systems: add golang platform dialect | aleksana | 2025-04-30 | 1 | -0/+29 |
| |/ |
|
| * | lib.systems.inspect.patterns.isEfi: add loongarch | aleksana | 2025-04-29 | 1 | -0/+5 |
| * | Revert "pkgs/top-level/stage.nix: add pkgsLLVMLibc"•••This reverts commit 41b14024d24bd7488b58d7a252f8f16b194d57f9.
| zowoq | 2025-04-24 | 3 | -7/+1 |
| * | lib.systems: force qemuArch to "aarch64" on aarch64•••qemu architecture names are fixed — we're using uname here just
because it's more likely to be correct than CPU name (see e.g. POWER).
This means that aarch64 is always called aarch64, even on Darwin where
uname reports arm64.
Fixes: 61582c704327 ("lib/systems: use Darwin architecture names for `config` and `uname`")
| Alyssa Ross | 2025-04-11 | 1 | -0/+2 |
| * | Merge remote-tracking branch 'origin/master' into staging-next | K900 | 2025-04-06 | 1 | -0/+4 |
| |\ |
|
| | * | lib.systems: Add arm-embedded-nano (#392204) | Maciej Krüger | 2025-04-06 | 1 | -0/+4 |
| | |\ |
|
| | | * | lib.systems: Add arm-embedded-nano•••Newlib-nano variant of the arm-embedded stdenv.
| Ross Smyth | 2025-03-20 | 1 | -0/+4 |
| * | | | lib/systems: use Darwin architecture names for `config` and `uname`•••`aarch64-apple-darwin` no longer works with LLVM 20.
| Emily | 2025-04-02 | 3 | -10/+16 |
| * | | | treewide: drop support for 32‐bit Darwin•••It’s dead, Jim.
| Emily | 2025-04-02 | 2 | -21/+0 |
| * | | | Merge staging-next into staging | nixpkgs-ci[bot] | 2025-04-02 | 1 | -89/+148 |
| |\| | |
|
| | * | | lib/systems/architecures: Add generic inferiors for x86-64 AMD | Mikael Voss | 2025-04-02 | 1 | -7/+7 |
| | * | | lib/system/architectures: Correct Alder Lake inferiors | Mikael Voss | 2025-04-02 | 1 | -2/+1 |
| | * | | lib/systems/architectures: Define inferiors for common ARM64 CPUs | Mikael Voss | 2025-04-02 | 1 | -121/+148 |
| | * | | lib/systems/architectures: Define generic ARM64 inferiors | Mikael Voss | 2025-04-02 | 1 | -1/+34 |
| * | | | Merge remote-tracking branch 'upstream/staging-next' into staging | Silvan Mosberger | 2025-04-02 | 6 | -877/+2111 |
| |\| | |
|
| | * | | treewide: Format all Nix files•••Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](https://github.com/NixOS/nixpkgs/tree/8616af08d915377bd930395f3b700a0e93d08728/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
| Silvan Mosberger | 2025-04-01 | 6 | -877/+2111 |
| | |/ |
|
| * / | lib.systems: mark LLVM libc as static | Tristan Ross | 2025-03-24 | 1 | -1/+1 |
| |/ |
|
| * | lib.systems.architectures: add sierra forest | Martin Fink | 2025-02-19 | 1 | -0/+2 |
| * | lib.systems: add znver5 architecture | Mathias Koehler | 2025-02-09 | 1 | -0/+2 |
| * | pkgs/top-level/stage.nix: add pkgsLLVMLibc | Tristan Ross | 2025-01-10 | 3 | -0/+5 |
| * | Merge remote-tracking branch 'origin/master' into staging-next | K900 | 2024-12-12 | 1 | -3/+3 |
| |\ |
|
| | * | lib/systems/parse.nix: mkSkeletonFromList: improve error message (#211213)•••Include the system string in the error message to give a bit more context to
the user.
Co-authored-by: Wolfgang Walther <wolfgangwalther@users.noreply.github.com> | Jean-François Roche | 2024-12-12 | 1 | -3/+3 |
| | * | treewide: format all inactive Nix files•••After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \
--argstr baseRev b32a0943687d2a5094a6d92f25a4b6e16a76b5b7
result/bin/apply-formatting $NIXPKGS_PATH
| Silvan Mosberger | 2024-12-10 | 1 | -20/+61 |
| * | | treewide: format all inactive Nix files•••After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build https://github.com/infinisil/treewide-nixpkgs-reformat-script/archive/a08b3a4d199c6124ac5b36a889d9099b4383463f.tar.gz \
--argstr baseRev 78e9caf153f5a339bf1d4c000ff6f0a503a369c8
result/bin/apply-formatting $NIXPKGS_PATH
| Silvan Mosberger | 2024-12-10 | 1 | -20/+61 |
| * | | Merge staging-next into staging | github-actions[bot] | 2024-11-30 | 1 | -6/+17 |
| |\| |
|
| | * | lib/systems: elaborate properly with non-matching system / config / parsed ar... | Philip Taron | 2024-11-29 | 1 | -6/+17 |
| | |\ |
|
| | | * | lib/systems: elaborate properly with non-matching system / config / parsed args•••When elaborating a system with both "config" and "system" arguments
given, they might not match the parsed results. Example:
elaborate {
config = "i686-unknown-linux-gnu";
system = "x86_64-linux";
}
This would result in a parsed system for i686, because the config
argument is preferred. But since "// args //" comes after system has
been inferred from parsed, it is overwritten again. This results in
config and parsed all pointing to i686, while system still tells the
story of x86_64.
Inconsistent arguments can also be given when passing "parsed" directly.
This happened in stage.nix for the various package sets.
The solution is simple: One of the three arguments needs to be treated
as the ultimate source of truth. "system" can already be losslessly
extracted from "parsed". However, "config" currently can not, for
example for various -mingw32 cases. Thus everything must be derived
from "config".
To do so, "system" and "parsed" arguments are made non-overrideable for
systems.elaborate. This means, that "system" will be used to parse when
"config" is not given - and "parsed" will be ignored entirely.
The systemToAttrs helper is exposed on lib.systems, because it's useful
to deal with top-level localSystem / crossSystem arguments elsewhere.
| Wolfgang Walther | 2024-11-03 | 1 | -6/+17 |
| * | | | Merge staging-next into staging | github-actions[bot] | 2024-11-27 | 2 | -1/+6 |
| |\| | |
|
| | * | | freebsd: Add support for aarch64 (#358053) | John Ericson | 2024-11-26 | 2 | -1/+6 |
| | |\ \ |
|
| | | * | | freebsd: Add support for aarch64•••Add a new `aarch64-freebsd` double and example system,
then fix include and libc to work.
This is enough to build packages like `hello`,
either static or dynamic.
This is useful for testing nix FreeBSD on a Raspberry Pi.
| Artemis Tosini | 2024-11-24 | 2 | -1/+6 |
| * | | | | Merge remote-tracking branch 'origin/staging-next' into staging | K900 | 2024-11-26 | 1 | -6/+7 |
| |\| | | |
|
