summary refs log tree commit diff
path: root/pkgs/stdenv/linux
Commit message (Collapse)AuthorAge
* Merge branch 'staging' into masterDaiderd Jordan2017-07-08
|\
| * cc-wrapper: improve response file parsing speedRyan Trinkle2017-06-30
| |
* | top-level: {build,host,target}Platform are defined in the stdenv insteadJohn Ericson2017-07-07
|/ | | | See #27069 for a discussion of this
* cross stdenv adaptor: Remove `ccCross` `binutils` attrs and binutils extra ↵John Ericson2017-06-22
| | | | | | buildDepends It now has the correct wrapped tools and nothing else is needed.
* cc-wrapper: Learn about target prefixesJohn Ericson2017-06-22
| | | | This is first step towards getting rid of gcc-wrapper-cross
* cc-wrapper: Remove `stdenv.is*` for `targetPlatform.is*`John Ericson2017-06-22
| | | | Modify bootstrapping stdenvs to make sure `targetPlatform` also passed.
* lib: Consolidate platform configurations (used for crossSystem)John Ericson2017-05-29
| | | | This is good for maintenance and education.
* stdenv: define is* predicates with hostPlatform.is*John Ericson2017-05-22
| | | | This is a saner default until stdenv's are removed altogether
* glibc: Fix for crossJohn Ericson2017-05-19
|
* linux cross stdenv: Use the cross stdenv and `nativeBuildInputs`John Ericson2017-05-17
| | | | | This is a cross derivation---it's built on one platform to run on another---so let's structure it like all the other cross derivations.
* linux cross stdenv: Fix eval errorsJohn Ericson2017-05-17
| | | | | | | | `pkgsNoParams` was removed by me, but then #25035 was merged using it, leading to an unbound identifier. It would be nice to get travis to do build release-cross.nix or something to catch these things.
* Merge pull request #25035 from elitak/cross-stagingMichael Raskin2017-05-01
|\ | | | | Add some ARM platforms
| * platforms: add pogoplug4 (armv5tel softfloat)Eric Litak2017-04-19
| |
| * platforms: add scaleway-c1 (armv7 sans NEON)Eric Litak2017-04-19
| |
* | binutils: Respect the targetPlatformJohn Ericson2017-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | Use `buildPackages.binutils` to get build = host != target binutils, i.e. the old `binutilsCross`, and use `buildPackages.buildPackages.binutils` to get build = host = target binutils, i.e. the old `binutils`. `buildPackages` chains like this are supposed to remove the need for all such `*Cross` derivations. We start with binutils because it's comparatively easy. No hashes of cross-tests should be changed
* | linux cross stdenv: Pull platforms from lib to cut eval timeJohn Ericson2017-04-25
| |
* | cross-stdenv: Only prune most overrides in the final stageJohn Ericson2017-04-24
|/ | | | | | | Before all overrides were also pruned in the previous stage, now only gcc and binutils are, because they alone care about about the target platform. The rest of the overrides don't, so it's better to preserve them in order to avoid spurious rebuilds.
* stdenv: ARM bootstrap: Update bootstrap tarballs to latest hydra-built onesTuomas Tynkkynen2017-04-15
| | | | | | | | | | | | | Fixes sandboxed build of glibc. Discussion about a similar failure on aarch64 at: https://github.com/NixOS/nixpkgs/commit/8bfa9f528c88243578246798c7c2ddde045e0de0. Picked from the following cross-trunk evaluation: http://hydra.nixos.org/eval/1349278 based on nixpkgs commit 1f32d4b4eb50a78613cc9a3866c4d50d03fbe2b0. armv5tel job: http://hydra.nixos.org/build/51569718 armv6l job: http://hydra.nixos.org/build/51569717 armv7l job: http://hydra.nixos.org/build/51569713
* make-bootstrap-tools.nix: Fix bzip2Tuomas Tynkkynen2017-04-13
| | | | Apparently our native bzip2 builds switched to using dynamic libraries at some point.
* stdenv: aarch64: Update bootstrap tarballsTuomas Tynkkynen2017-03-15
| | | | | | | | | | | | | Hopefully fixes sandboxed build of glibc on aarch64, as discussed on https://github.com/NixOS/nixpkgs/commit/8bfa9f528c88243578246798c7c2ddde045e0de0. Picked from the following cross-trunk evaluation: http://hydra.nixos.org/eval/1341395 based on nixpkgs commit bb3ef8a95c9659596b8a34d27881cd30ffea2f9f. build job: http://hydra.nixos.org/build/50125932 (busybox's hash not changing is not a bug!)
* make-bootstrap-tools{,-cross}.nix: Fix build after binutils changesTuomas Tynkkynen2017-02-04
| | | | Broken after commit 17a344a ("binutils: Add lib output").
* stdenv: Aarch64 bootstrap: Update bootstrap tarballs to hydra-built onesTuomas Tynkkynen2017-01-29
| | | | | | | | Picked from the following cross-trunk evaluation: http://hydra.nixos.org/eval/1326772#tabs-still-succeed based on nixpkgs commit 264d42b9cfc3edf16e945164a45b31185e47422a. dist job: http://hydra.nixos.org/build/47094514
* Merge pull request #22117 from dezgeg/aarch64-for-mergeTuomas Tynkkynen2017-01-26
|\ | | | | Aarch64 (ARM64) support
| * stdenv: Add aarch64 bootstrap filesTuomas Tynkkynen2017-01-25
| | | | | | | | | | These are temporary and will be switched to Hydra-build ones once all the aarch4 changs are merged.
| * make-bootstrap-tools.nix test: Use busybox from storeTuomas Tynkkynen2017-01-25
| | | | | | | | | | | | | | | | Our bootstrap tools are actually broken right now due to busybox not working when invoked directly from a store path. (It says e.g. "0qqqw19y4gmknajw8vg4fvhx9gxdqlhz-busybox: applet not found"). Make this test actually fail in such case, the next commit will fix the problem with busybox.
| * stdenv: Add updateAutoconfGnuConfigScriptsHook for aarch64Tuomas Tynkkynen2017-01-25
| | | | | | | | | | | | | | | | | | | | | | This is required for Aarch64 since a lot of source tarballs ship with outdated configure scripts that don't recognize aarch64. Simply replacing the config.guess and config.sub with new versions from upstream makes them build again. This same approach is used by at least Buildroot and Fedora. In principle this could be enabled for all architectures but conditionalizing this on aarch64 avoids a mass rebuild on x86.
| * stdenv: Bringup aarch64 architecture supportTuomas Tynkkynen2017-01-25
| |
* | top-level: no more need to expose `splicedPackages`John Ericson2017-01-25
|/ | | | | This was just done temporarily on the last cross-overhauling PR for testing purposes.
* top-level: `crossSystem` is no longer exposed to packages. Use `*Platform`.John Ericson2017-01-24
|
* top-level: Lay the groundwork for `{build,host,target}Platform`John Ericson2017-01-24
| | | | | | | | | | | | The long term goal is a big replace: { inherit system platform; } => buildPlatform crossSystem => hostPlatform stdenv.cross => targetPlatform And additionally making sure each is defined even when not cross compiling. This commit refactors the bootstrapping code along that vision, but leaves the old identifiers with their null semantics in place so packages can be modernized incrementally.
* top-level: Introduce `buildPackages` for resolving build-time depsJohn Ericson2017-01-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | [N.B., this package also applies to the commits that follow it in the same PR.] In most cases, buildPackages = pkgs so things work just as before. For cross compiling, however, buildPackages is resolved as the previous bootstrapping stage. This allows us to avoid the mkDerivation hacks cross compiling currently uses today. To avoid a massive refactor, callPackage will splice together both package sets. Again to avoid churn, it uses the old `nativeDrv` vs `crossDrv` to do so. So now, whether cross compiling or not, packages with get a `nativeDrv` and `crossDrv`---in the non-cross-compiling case they are simply the same derivation. This is good because it reduces the divergence between the cross and non-cross dataflow. See `pkgs/top-level/splice.nix` for a comment along the lines of the preceding paragraph, and the code that does this splicing. Also, `forceNativeDrv` is replaced with `forceNativePackages`. The latter resolves `pkgs` unless the host platform is different from the build platform, in which case it resolves to `buildPackages`. Note that the target platform is not important here---it will not prevent `forcedNativePackages` from resolving to `pkgs`. -------- Temporarily, we make preserve some dubious decisions in the name of preserving hashes: Most importantly, we don't distinguish between "host" and "target" in the autoconf sense. This leads to the proliferation of *Cross derivations currently used. What we ought to is resolve native deps of the cross "build packages" (build = host != target) package set against the "vanilla packages" (build = host = target) package set. Instead, "build packages" uses itself, with (informally) target != build in all cases. This is wrong because it violates the "sliding window" principle of bootstrapping stages that shifting the platform triple of one stage to the left coincides with the next stage's platform triple. Only because we don't explicitly distinguish between "host" and "target" does it appear that the "sliding window" principle is preserved--indeed it is over the reductionary "platform double" of just "build" and "host/target". Additionally, we build libc, libgcc, etc in the same stage as the compilers themselves, which is wrong because they are used at runtime, not build time. Fixing this is somewhat subtle, and the solution and problem will be better explained in the commit that does fix it. Commits after this will solve both these issues, at the expense of breaking cross hashes. Native hashes won't be broken, thankfully. -------- Did the temporary ugliness pan out? Of the packages that currently build in `release-cross.nix`, the only ones that have their hash changed are `*.gcc.crossDrv` and `bootstrapTools.*.coreutilsMinimal`. In both cases I think it doesn't matter. 1. GCC when doing a `build = host = target = foreign` build (maximally cross), still defines environment variables like `CPATH`[1] with packages. This seems assuredly wrong because whether gcc dynamically links those, or the programs built by gcc dynamically link those---I have no idea which case is reality---they should be foreign. Therefore, in all likelihood, I just made the gcc less broken. 2. Coreutils (ab)used the old cross-compiling infrastructure to depend on a native version of itself. When coreutils was overwritten to be built with fewer features, the native version it used would also be overwritten because the binding was tight. Now it uses the much looser `BuildPackages.coreutils` which is just fine as a richer build dep doesn't cause any problems and avoids a rebuild. So, in conclusion I'd say the conservatism payed off. Onward to actually raking the muck in the next PR! [1]: https://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html
* Fix missing overlays argument in stdenv/linux/default.nixNicolas B. Pierron2017-01-16
|
* Add overlays mechanism to Nixpkgs.Nicolas B. Pierron2017-01-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
* linux stdenv: Inline stage funs to conform to new conventionJohn Ericson2017-01-13
| | | | Code is just moved around
* linux stdenv: Remove stray use of stage0 to bootstrap more elegantlyJohn Ericson2017-01-13
|
* linux stdenv: Utilize overrides and prevStage betterJohn Ericson2017-01-13
| | | | | | | | `gcc-unwrapped` basically replaces `gccPlain`. It may seem like an ugly polution to stick it in all-packages, but a future PR will enshrine this `*-unwrapped` pattern. In any event, the long term goal is stdenvs might need to tweak how compilers are booted and wrapped, but the code to build the unwrapped compilers themselves should be generic.
* top-level: Normalize stdenv bootingJohn Ericson2017-01-13
| | | | | | | | | | | Introduce new abstraction, `stdenv/booter.nix` for composing bootstraping stages, and use it everywhere for consistency. See that file for more doc. Stdenvs besides Linux and Darwin are completely refactored to utilize this. Those two, due to their size and complexity, are minimally edited for easier reviewing. No hashes should be changed.
* top-level: Modernize stdenv.overrides giving it self and superJohn Ericson2017-01-13
| | | | Document breaking change in 17.03 release notes
* coreutils: Build with libattr to support xattrsTuomas Tynkkynen2017-01-05
| | | | Fixes #21649
* linux stdenv: Avoid `assert false`John Ericson2016-12-15
| | | | | | | On one hand, don't want to pass garbage that affects hash, on the other hand footguns are bad. Now, factored out the derivation so only need to pass in what is used.
* linux stdenv: Rename the `bootstrap` directory to `bootstrap-files`John Ericson2016-12-15
|
* linux stdenv: Fix assert that broke tests...and hydraJohn Ericson2016-12-15
|
* top-level: Allow manually specifying a stdenv, and fix stdenv testsJohn Ericson2016-12-03
| | | | | | | - The darwin test can now force the use of the freshly-booted darwin stdenv - The linux test now passes enough dummy arguments This may make debugging harder, if so, check out #20889
* top-level: turn the screwJohn Ericson2016-12-01
| | | | | | | | | | | | - Non-cross stdenvs are honest and assert that `crossSystem` is null - `crossSystem` is a mandatory argument to top-level/stage.nix, just like `system` and `platform` - Broken default arguments on stdenvs for testing are gone. - All stdenvs (but little-used stdenvNix) take the same arguments for easy testing.
* top-level: Close over fewer arguments for stdenv stagesJohn Ericson2016-11-30
| | | | | | | | This makes the flow of data easier to understand. There's little downside because the args in question are already inspected by the stdenvs. cross-compiling in particular is simpler because we don't need to worry about overriding the config closed over by `allPackages`.
* top-level: Remove cycles: stdenv calls in top-level but not vice versaJohn Ericson2016-11-30
| | | | | | | | | | | | | | | | | | | | | | | This commit changes the dependencies of stdenv, and clean-up the stdenv story by removing the `defaultStdenv` attribute as well as the `bootStdenv` parameter. Before, the final bootstrapping stage's stdenv was provided by all-packages, which was iterating multiple times over the top-level/default.nix expression, and non-final bootstrapping stages' stdenvs were explicitly specified with the `bootStdenv` parameter. Now, all stages' stdenvs are specified with the `stdenv` parameter. For non-final bootstrapping stages, this is a small change---basically just rename the parameter. For the final stage, top-level/default.nix takes the chosen stdenv and makes the final stage with it. `allPackages` is used to make all bootstrapping stages, final and non-final alike. It's basically the expression of `stage.nix` (along with a few partially-applied default arguments) Note, the make-bootstrap-tools scripts are temporarily broken
* make-bootstrap-tools-cross.nix: Fix gcc build-time options for armv5telTuomas Tynkkynen2016-08-28
| | | | | | I broke this in the cleanups I did in 171c7f0, the gcc inside the bootstrap tarball is not getting built with the correct --with-fpu, --with-float etc. options.
* stdenv: ARM bootstrap: Update bootstrap tarballs to hydra-built onesTuomas Tynkkynen2016-07-20
| | | | | | | | | | Picked from the following cross-trunk evaluation: http://hydra.nixos.org/eval/1283982#tabs-inputs based on nixpkgs commit 33a1d8080b50bdbf0143f4513db2fb4fe3acbd2e. armv5tel job: http://hydra.nixos.org/build/37908177 armv6l job: http://hydra.nixos.org/build/37908176 armv7l job: http://hydra.nixos.org/build/37908175
* make-bootstrap-tools{,-cross}.nix: Create deterministic tarsTuomas Tynkkynen2016-07-20
|
* make-bootstrap-tools-cross.nix: Support 'dist' targetTuomas Tynkkynen2016-07-20
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-25 01:11:41 +0000