John Ericson adaa110a72 binutils: No more darwin conditionals ... Since at least d7bddc27b2, 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.		2018-04-03 13:34:52 -04:00
..
darwin-secure-format.patch	Fix Darwin stdenv to work on 10.13	2017-07-11 21:56:38 -04:00
default.nix	binutils: No more darwin conditionals	2018-04-03 13:34:52 -04:00
make-bootstrap-tools.nix	darwin bootstrap tools: fix after #34339 (http2 in curl)	2018-02-10 19:20:44 +01:00
unpack-bootstrap-tools.sh	darwin stdenv: Ensure libSystem reexports the right libraries	2017-07-25 14:35:43 -04:00