| Commit message (Collapse) | Author | Age |
|\ |
|
| | |
|
|\| |
|
| | |
|
| |
| |
| |
| |
| |
| | |
- tracing seems annoying enough
- we get errors for all packages instead of aborting on the first one
- easier to differentiate from unwanted packages (broken, unfree, etc.)
|
| |
| |
| |
| | |
for some reason we were checking allowUnfreePredicate instead
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
stdenv setup: Always use both propagated files
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This continues #23374, which always kept around both attributes, by
always including both propagated files: `propgated-native-build-inputs`
and `propagated-build-inputs`. `nativePkgs` and `crossPkgs` are still
defined as before, however, so this change should only barely
observable.
This is an incremental step to fully keeping the dependencies separate
in all cases.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* master: (293 commits)
go_1_9: skip flaky TestServerCancelsReadTimeoutWhenIdle
qsyncthingtray: fix build
qt56.qtwebengine: fix build
stdman: d860212 -> 2017.04.02
jackett: use mono50
hg-git: disable with python3
hg-git: 0.8.5 -> 0.8.10
xfce4-settings: enable parallel building
gcc-snapshot: mark as broken
heaptrack: 2017-02-14 -> 2017-10-30
nixos-container: Modify existing test to cover show-ip command
nixos-container: Make show-ip work together with ipv4 + netmask
linux-copperhead: 4.13.12.a -> 4.13.13.a
matterbridge: 1.1.0 -> 1.4.1
nixos/nghttpx: add module for the nghttpx proxy server (#31680)
mattermost: 4.3.0 -> 4.4.0
breakpad: delete
simp_le: 0.2.0 -> 0.6.1
certbot: 0.11.1 -> 0.19.0
afl: 2.51b -> 2.52b
...
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/| |
stdenv setup: Run setup hooks and other processing after accumulating deps
|
| | |
| | |
| | |
| | |
| | |
| | | |
I find the separation of concerns, accumulating, then processing, easier
to follow. Also, with my yet-to-be-merged cross work, the accumulation
part will become more complex.
|
| | | |
|
|\| |
| | |
| | | |
bfd, opcodes: Init separate derivations for binutils libraries
|
| |/ |
|
| | |
|
|/
|
|
| |
This is the first step to getting a sandboxable nixpkgs
|
| |
|
|
|
|
|
|
|
|
|
| |
directly
One should do this when needed executables at run time. It is more
honest and cross-friendly than refering to binutils directly, if one
neeeds the default binary tools for the target platform, rather than
binutils in particular.
|
| |
|
|
|
|
|
|
| |
This requires some small changes in the stdenv, then working around the
weird choice LLVM made to hardcode @rpath in its install name, and then
lets us remove a ton of annoying workaround hacks in many of our Go
packages. With any luck this will mean less hackery going forward.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cc-wrapper may wrap a cc-compiler, but it doesn't need one to build
itself. (c.f. expand-response-params is a separate derivation.) This
helps avoid cycles on the cross stuff, in addition to removing a
useless dependency edge.
I could have been super careful with overrides in the stdenv to avoid
the mass rebuild, but I don't think it's worth it.
|
| |
| |
| |
| |
| |
| | |
Why 6? It seems a decently high number, giving us room for more degrees
of debugging before the `set -x` sledgehammer without incurring a
mass-rebuild.
|
| | |
|
|/
|
|
|
| |
The comment says it was put there for pkgconfig, but now pkgconfig has
been dealt with.
|
| |
|
|
|
|
|
| |
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
|