Adam Joseph 23ea8b35da stdenv: label the ephemeral coreutils-stage4 package ... During stdenv bootstrapping, coreutils is built twice. This makes troubleshooting very difficult, because both packages have name="coreutils", so it is a hassle to figure out "which coreutils am I using / is not building"? The first of these builds is used only in stage4, and is not part of the final stdenv. Let's label that one with a different `name` attribute to make it obvious which is which.		2022-06-05 00:35:06 -07:00
..
cross	llvmPackages_*: respect cc for target when choosing C++ flavour	2022-01-07 14:42:41 +01:00
custom
cygwin
darwin	Merge staging-next into staging	2022-05-31 18:01:50 +00:00
freebsd	config.contentAddressedByDefault: init option	2022-04-27 23:21:32 +03:00
generic	Merge staging-next into staging	2022-06-02 00:03:03 +00:00
linux	stdenv: label the ephemeral coreutils-stage4 package	2022-06-05 00:35:06 -07:00
native
nix
adapters.nix	treewide: stdenv.glibc -> glibc	2022-05-25 15:51:20 +03:00
booter.nix	llvmPackages_*: respect cc for target when choosing C++ flavour	2022-01-07 14:42:41 +01:00
common-path.nix	fixLibtool(): patch ./configure, add file to common-path.nix	2022-05-26 13:53:36 -07:00
default.nix	lib/systems: add mips64el definitions	2022-03-10 20:30:16 -08:00