| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
stdenv, binutils: Build cctools targeting macOS on Linux without pointless rebuilds
|
| | |
| |
| |
| |
| |
| |
| | |
We want `buildPackages` to be almost the same as
`buildPackages.buildPackges`, but that is only true if most packages
don't care about the target platform. The commented code however made
them all care about whether the target platform was Darwin.
|
| |\|
| |
| | |
darwin stdenv: Properly compose overrides
|
| | |
| |
| |
| | |
`super` usage was very suspect.
|
| |\| |
|
| | |
| |
| |
| |
| | |
binutils-unwrapped was added in ef3db7d14c90e1876d38ebc25428b4f65962ffbc
and needs a corresponding `persisted` attr in the Darwin stdenv.
|
| |\|
| |
| |
| |
| | |
Conflicts:
pkgs/top-level/all-packages.nix
|
| | | |
|
| | |
| |
| |
| | |
All its uses have been removed.
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
gnu-config: Update, allowing hacks to be removed
|
| | | |\| |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Broke the stdenv.
This reverts commit 69d1b7ab79cc5e46d4b419cfe95c30e58f801a85.
|
| | |\ \ \
| | | |/
| | |/| |
|
| | | |\ \
| | | | |
| | | | | |
stdenv: Put back isArm, with deprecation notice.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
treewide: Modular setup hooks
|
| | | |/ / / |
|
| | | | | | |
|
| | |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | |\ \ \
| | | | | |
| | | | | | |
stdenv: implement most of #33599
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Note that a bunch of non-python packages use this attribute already.
Some of those are clearly unaware of the fact that this attribute does
not exists in stdenv because they define it but don't to add it to
their `bulidInputs` :)
Also note that I use `buildInputs` here and only handle regular
builds because python and haskell builders do it this way and I'm not
sure how to properly handle the cross-compilation case.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | |\ \ \ \
| | | | | | |
| | | | | | | |
stdenv: change texinfo bootstrap handling; texinfo, bash: simplify expressions
|
| | | | |/ / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This makes stdenv bootstraping a bit more efficient.
We don't recompile most of other stuff used in bootstrapping stdenv too.
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As in:
$ nix eval -f . bash
Also remove the glibc propagation inherit that made these necessary,
stages handle propagating libc themselves (apparently) and
AFAICT no hashes are changed as a result of this.
|
| | | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Conflicts:
pkgs/development/tools/misc/binutils/default.nix
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 6c064e6b1f34a8416f990db0cc617a7195f71588, reapplying
PR #28029 which was supposed to have gone to staging all along.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
|
| | | | | | | |
|
| | | |/ / /
| |/| | | |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
ios-sdk-pkgs: Init from iOS SDK from XCode
|
| | | | | | | |
|
| | |\ \ \ \ \
| | |/ / / /
| |/| | | | |
nixpkgs module: Clean up platform options
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- `localSystem` is added, it strictly supercedes system
- `crossSystem`'s description mentions `localSystem` (and vice versa).
- No more weird special casing I don't even understand
TEMP
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
Fix stdenv-native and fix rebasing on cygwin
|
| | | | | | | | |
|
| | | | |/ / /
| | |/| | | |
|
| | |\ \ \ \ \
| | |/ / / /
| |/| | | | |
meta: Don't bypass unsupported platforms with allowBroken.
|
| | | | | | | |
|
| | | |/ / /
| | | | |
| | | | |
| | | | | |
Our platforms are open-world oriented these days, and anyway there's allowUnsupportedSystem.
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since at least d7bddc27b23da8ce7bc19cfeeeb0cbebdb5a4410, we've had a
situation where one should depend on:
- `stdenv.cc.bintools`: for executables at build time
- `libbfd` or `libiberty`: for those libraries
- `targetPackages.cc.bintools`: for exectuables at *run* time
- `binutils`: only for specifically GNU Binutils's executables,
regardless of the host platform, at run time.
and that commit cleaned up this usage to reflect that. This PR flips the
switch so that:
- `binutils` is indeed unconditionally GNU Binutils
- `binutils-raw`, which previously served that role, is gone.
so that the correct usage will be enforced going forward and everything
is simple.
N.B. In a few cases `binutils-unwrapped` (which before and now was
unconditionally actual GNU binutils), rather than `binutils` was used to
replace old `binutils-raw` as it is friendly towards some cross
compilation usage by avoiding a reference to the next bootstrapping
change.
|
| | | | |
| | | |
| | | |
| | | | |
Code golf or readability, you decide
|
| | | | | |
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | | |
lib: Factor in tiny bit of `meta.platform` checking
|