| Commit message (Collapse) | Author | Age |
|\ |
|
| | |
|
| |
| |
| |
| | |
Fixes #85038
|
|/
|
|
|
|
|
|
|
|
| |
If the option ‘noclobber’ is set in Bash, we get an error when we
clobber an already existing env-vars. This is an okay error to ignore,
so just >| instead. Note that >| is NOT a Bashism[[1]].
Fixes #79651
[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_02
|
|
|
|
|
|
|
|
| |
These files never existed, so best to not leave the reference. If
someone want to step up to maintain this, that would be fine. I don’t
have the hardware to test these out. In addition, someone tried to use
the bootstrap-tools currently built by Hydra and found that they were
broken in some unclear way.
|
|
|
|
| |
Co-authored-by: Cole Helbling <cole.e.helbling@outlook.com>
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
The linker scripts no longer contain store paths, so this does nothing. More
importantly, libpthread.so is not longer a linker script on ARM, so the patching
would corrupt it.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes building glibc 2.30, which requires at least GCC 6.
Picked from the following cross-trunk evaluation:
https://hydra.nixos.org/eval/1568864 based on nixpkgs
commit ac241fb7a57.
armv5tel job: https://hydra.nixos.org/build/111556418
armv6l job: https://hydra.nixos.org/build/111556521
armv7l job: https://hydra.nixos.org/build/111556551
|
|/ |
|
|
|
|
|
|
| |
There's a generated header that got comment about the source header
from glibc.dev, which added unwanted runtime dependency. Tested:
nix build -f pkgs/top-level/release.nix stdenvBootstrapTools.{aarch64,i686,x86_64}-linux.test
|
|\ |
|
| |
| |
| |
| |
| | |
isArm has been deprecated for three releases. All references have been
removed. Tree-wide substitution was performed in #37401 21 months ago.
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Includes update of stdenv bootstap tools (for three main platforms)
and many package fixes with new glibc.
|
| |
| |
| |
| |
| |
| | |
From Hydra's binaries for c5aabb0 (19.09).
This time I re-tested full stdenv bootstrap on these three platforms.
https://github.com/NixOS/nixpkgs/pull/66528#issuecomment-582351637
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The old bootstrapping files would break with glibc 2.30 as at least gcc6
is needed.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It's a bit hacky, but ATM I can't see any better way for glibc >= 2.28.
Signed-off-by: Luka Blaskovic <lblasc@tvbeat.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
There's a failure - I don't know why. The checks from "normal" dejagnu
still succeed, so I assume this commit is quite a safe work-around.
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This was initially introduced in 92188d9d1751892ddbf8913da73dfc150d18fadb,
not clear how relevant this still is but i686 isn't supported anymore so
disable it explicitly.
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #21629
Passing these extra linker flags removes both the semi-random uuid
included in most binaries as well as making the sdk version consistent
instead of based on the current os version.
Load command 8
cmd LC_UUID
cmdsize 24
uuid 70FAF921-5DC8-371C-B814-4F121FADFDF4
Load command 9
cmd LC_VERSION_MIN_MACOSX
cmdsize 16
version 10.12
sdk 10.13
The -macosx_version_min flag isn't strictly necessary since that's
already handled by MACOSX_DEPLOYMENT_TARGET.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While looking at the graph of all the outputs in my personal binary
cache it became obvious that we have a lot of self references within the
package set. That isn't an isuse by itself. However it increases the
size of the binary cache for every (reproducible) build of a package
that carries references to itself. You can no longer deduplicate the
outputs since they are all unique. One of the ways to get rid of (a few)
references is to rewrite all the symlinks that are currently used to be
relative symlinks. Two build of something that didn't really change but
carries a self-reference can the be store as the same NAR file again.
I quickly hacked together this change to see if that would yield and
success. My bash scripting skills are probably not great but so far it
seem to somewhat work.
|
|\ \
| |/
|/| |
darwin-stdenv: bootstrap with python3
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Replaced python override from the final stdenv, instead we
propagate our bootstrap python to stage4 and override both
CF and xnu to use it.
- Removed CF argument from python interpreters, this is redundant
since it's not overidden anymore.
- Inherit CF from stage4, making it the same as the stdenv.
|
|/ |
|
|\
| |
| | |
stdenv, haskell: bonafied GHCJS cross compilation without stdenv.cc
|
| |\
| | |
| | |
| | | |
ghcjs-cross-without-cc
|
| | | |
|
| |\|
| | |
| | |
| | | |
ghcjs-cross-without-cc
|
| | |
| | |
| | |
| | | |
js-ghcjs didn't fit in an existing categor.
|
| |\ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | | |
This platform doesn't have a C compiler, and so relies and the changes
in the previous commit to work.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before, we'd always use `cc = null`, and check for that. The problem is
this breaks for cross compilation to platforms that don't support a C
compiler.
It's a very subtle issue. One might think there is no problem because we
have `stdenvNoCC`, and presumably one would only build derivations that
use that. The problem is that one still wants to use tools at build-time
that are themselves built with a C compiler, and those are gotten via
"splicing". The runtime version of those deps will explode, but the
build time / `buildPackages` versions of those deps will be fine, and
splicing attempts to work this by using `builtins.tryEval` to filter out
any broken "higher priority" packages (runtime is the default and
highest priority) so that both `foo` and `foo.nativeDrv` works.
However, `tryEval` only catches certain evaluation failures (e.g.
exceptions), and not arbitrary failures (such as `cc.attr` when `cc` is
null). This means `tryEval` fails to let us use our build time deps, and
everything comes apart.
The right solution is, as usually, to get rid of splicing. Or, baring
that, to make it so `foo` never works and one has to explicitly do
`foo.*`. But that is a much larger change, and certaily one unsuitable
to be backported to stable.
Given that, we instead make an exception-throwing `cc` attribute, and
create a `hasCC` attribute for those derivations which wish to
condtionally use a C compiler: instead of doing `stdenv.cc or null ==
null` or something similar, one does `stdenv.hasCC`. This allows quering
without "tripping" the exception, while also allowing `tryEval` to work.
No platform without a C compiler is yet wired up by default. That will
be done in a following commit.
|
| |/
|/|
| |
| |
| | |
this allows correct operation with packages only having pname and version
specified, resolving issue #73737
|
| |
| |
| |
| |
| |
| |
| |
| | |
Rewrite the `stripHash` helper function with 2 differences:
* Paths starting with `--` will no longer produce an error.
* Use Bash string manipulation instead of shelling out to `grep` and
`cut`. This should be faster.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A bunch of stdenv-internal variables were deleted in
1601a7fcce389ae3f1b1b36676fd5545035566af, but these are needed in the
fixup phase, whereas the rest are just needed for the initial work
(findInputs, etc) before the user phases.
CC @matthewbauer
|
|\ \
| | |
| | | |
Unset unused variables in setup.sh
|
| | |
| | |
| | |
| | |
| | |
| | | |
setup.sh adds a bunch of variables that only it needs. To avoid
polluting environments, we should unset these as soon as we are done
with them.
|
|\ \ \ |
|
| | | |
| | | |
| | | | |
This reverts commit 71184f8e157672789602d3f28bdd3c8079800687.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There were two issues:
* builtins.getEnv was called deep into the nixpkgs tree making it hard
to discover. This is solved by moving the call into
pkgs/top-level/impure.nix
* when the config was explicitly set by the user to false, it would
still try and load the environment variable. This meant that it was
not possible to guarantee the same outcome on two different systems.
|
| |\ \ \
| | | | |
| | | | | |
Fix handling of lists in whitelistedLicenses and blacklistedLicenses
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A package's meta.license can either be a single license or a list. The
code to check config.whitelistedLicenses and config.blackListedLicenses
wasn't handling this, nor was the showLicense function.
|