| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
They, unlike their native counterparts, run on the wrong platform and
are therefore invalid.
|
|
|
|
|
|
| |
By default, all previous overrides are discarded as before, as they
would only apply to the old host platform. But sometimes it is useful to
add some new ones, and this optional parameter allows that.
|
|
|
|
|
|
|
| |
This is needed when cross-compiling for iOS (Aarch64 + Darwin). I also
changed the syntax of the Linux stdenv for visual consistency, though
that has no effect on semantics as the os is already guaranteed to be
Linux.
|
|
|
|
|
| |
I messed this up when I moved the logic from `makeStdenvCross` in
e826a6a24774.
|
| |
|
|
|
|
|
|
|
| |
- Compiler's shouldn't use `binutils.dev` as that doesn't yet exist
with a cross binutils.
- Last two `binutils.binutils` which weren't reverted
|
|
|
|
|
| |
This is probably a fallout from #28557 merge and revert.
I can't see why exactly this happened, but it seems a safe fix.
|
|
|
|
|
|
| |
This allows the progress bar to show e.g.
[1/9/59 built] building bison-3.0.4 (configurePhase): checking for strdup... yes
|
|
|
|
| |
This has not been used in a long time.
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 0a944b345e89ca0096974d168f49e1c6830c3fc2, reversing
changes made to 61733ed6ccde3427016720f2e0cd191d3d95152c.
I dislike these massive stdenv changes with unclear motivation,
especially when they involve gratuitous mass renames like NIX_CC ->
NIX_BINUTILS. The previous such rename (NIX_GCC -> NIX_CC) caused
months of pain, so let's not do that again.
|
|
|
|
| |
Now the NixOS tarball job succeeds again
|
|\
| |
| | |
Binutils-wrapper: Init by refactoring out of cc-wrapper
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Environment variable filter in substituteAll was not precise and produced
undefined and invalid variable names. Vladimír Čunát tried to fix that in [1],
but `env -0` did not work during Darwin bootstrap, so [2] reverted this change
and replaced an error due to invalid variables with a warning. Recently in #28057
John Ericson added `set -u` to `setup.sh` and undefined variables made the setup
fail during e.g. `nix-build -A gnat` with `setup: line 519: !varName: unbound
variable`.
[1] https://github.com/NixOS/nixpkgs/commit/62fc8859c10dd18b005b9bcaa0b429103d7661d9
[2] https://github.com/NixOS/nixpkgs/commit/81df0354290389128077e00edfd2368eeeea0c24
|
|/
|
|
| |
https://github.com/NixOS/nixpkgs/pull/28806#discussion_r136516276
|
|
|
|
|
|
|
|
| |
- allow "all" in hardeningDisable
- fix busybox flags
- print detailed error message
Discussed at https://github.com/NixOS/nixpkgs/pull/28555#issuecomment-326413032
|
| |
|
|
|
|
| |
Now, we'll actually use the wrapped ld to link
|
|
|
|
|
|
|
|
|
| |
This becomes necessary if more wrappers besides cc-wrapper start
supporting hardening flags. Also good to make the warning into an
error.
Also ensure interface is being used right: Not as a string, not just in
bash.
|
|
|
|
| |
NIX_COREFOUNDATION_RPATH
|
| |
|
|\
| |
| | |
stdenv-setup: use `set -u`
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Older bash version, like those in the bootstrap tools and on macOS,
currently confuse variables defined as an empty array with undefined
variables. `${foo+"${foo[@]}"}` will prevent `set -u` problems with
empty arrays and older without making a single '' in the empty case.
Care is taken to `set +u` when running hooks so as to not break existing
packages.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Don't build with libsigsegv by default. The build apparently attempted
to link against it, but it never retained the reference anyway...
- Side effect: stdenv bootstrapping needs no libsigsegv anymore.
- Run checks, but only in the interactive gawk by default on Linux,
so that stdenv bootstrap isn't slowed down (by glibc locales, etc.).
- xz should be no longer needed in inputs, as we have it in stdenvs now.
The whole change was triggered by some used kernel versions still
breaking libsigsegv tests #28464.
|
|/
|
|
| |
No need for silly differences.
|
|\
| |
| |
| | |
That way the tarball job succeeds
|
| |
| |
| |
| | |
Ensured hashes unchanged and eval succeeds in tarball job
|
| |\ |
|
|\| | |
|
| | | |
|
| |/
|/|
| |
| |
| | |
This version continues to use bash + stdenv/setup for the default
inputs.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`extraNativeBuildInputs`"
This reverts commit eeabf85780e7fccc0289b4015b695e28ef166ab7.
This change suddenly makes tons of stdenv internals visible in
nativeBuildInputs of every derivation, which doesn't seem desirable.
E.g:
````
nix-repl> hello.nativeBuildInputs
[ «derivation /nix/store/bcfkyf6bhssxd2vzwgzmsbn7b5b9rpxc-patchelf-0.9.drv»
«derivation /nix/store/4wnshnz9wwanpfzcrdd76rri7pyqn9sk-paxctl-0.9.drv»
<< snip 10+ lines >>
«derivation /nix/store/d35pgh1lcg5nm0x28d899pxj30b8c9b2-gcc-wrapper-6.4.0.drv»
]
````
|
|\ \
| | |
| | | |
enable hydra jobs for packages x86_64-linux does not support
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently the logic of generating nixpkgs Hydra jobs is to walk through
the pkgs evaluated for system = "x86_64-linux", collect any derivations
and their meta.platforms values. However, that doesn't work for
packages whose meta.platforms doesn't include x86_64-linux, as just
evaluating their meta attribute raises an error so they get skipped
completely.
As a less-intrusive fix (i.e. anything than rewriting the current package
enumeration logic), allow passing `config.allowUnsupportedSystem = true`
to permit evaluating packages regardless of their platform and use that
in the package listing phase.
Fixes #25200
|
|\ \ \
| | |/
| |/| |
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
Additionally, instead of pulling them from `setup.sh`, route them via
Nix. This gets us one step closer to making stdenv be a plain attribute
set instead of a derivation.
|
| |
| |
| |
| | |
No hashes were changed by this
|
| | |
|
|/
|
|
| |
Discovered in #28091. I'm sorry I forgot to re-check my TODOs, long ago.
|
| |
|
|
|
|
| |
See the added comments for what exactly has been done.
|
|\ |
|
| |
| |
| |
| |
| | |
Probably best to override Haskell packages set, or anything else
linking a lot of libraries, with this.
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
pkgs/build-support/cc-wrapper/default.nix
pkgs/build-support/gcc-wrapper-old/builder.sh
pkgs/build-support/trivial-builders.nix
pkgs/desktops/kde-4.14/kde-package/default.nix
pkgs/development/compilers/openjdk-darwin/8.nix
pkgs/development/compilers/openjdk-darwin/default.nix
pkgs/development/compilers/openjdk/7.nix
pkgs/development/compilers/openjdk/8.nix
pkgs/development/compilers/oraclejdk/jdk-linux-base.nix
pkgs/development/compilers/zulu/default.nix
pkgs/development/haskell-modules/generic-builder.nix
pkgs/misc/misc.nix
pkgs/stdenv/generic/builder.sh
pkgs/stdenv/generic/setup.sh
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's better than the eval solution this is adding back, but until we can
rely on a particular version of bash in nix-shell, this just breaks too
much stuff.
See https://github.com/NixOS/nix/commit/c94f3d5575d7af5403274d1e9e2f3c9d72989751
and https://github.com/NixOS/nix/pull/1483 for the better long-term
solution.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As @oxij points out in [1], this breakage is especially serious because
it changes the contents of built environments without a corresonding
change in their hashes. Also, the revert is easier than I thought.
This reverts commit 3cb745d5a69018829ac15f7d5a508135f6bda123.
[1]: https://github.com/NixOS/nixpkgs/pull/27427#issuecomment-317293040
|
| |
| |
| |
| |
| | |
This is invalid before bash-4.2, affecting bash used impurely in
nix-shell on MacOS.
|