public
/
nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nixpkgs/pkgs/test/simple/default.nix

18 lines
309 B
Nix
Raw Normal View History

* Started reorganising stdenv: - gcc/ld-wrappers have been factored out into a separate derivation. This allows a working gcc to be installed in the user environment. (Previously the Nix gcc didn't work because it needed a whole bunch of flags to point to glibc.) - Better modularity: packages can specify hooks into the setup scripts. For instance, setup no longer knows about the PKG_CONFIG_PATH variable; pkgconfig can set it up instead. - gcc not longer depends on binutils. This simplifies the bootstrap process. svn path=/nixpkgs/trunk/; revision=816
2004-03-08 08:02:46 -08:00
let {
system = "i686-linux";
* stdenv-nix-linux should more-or-less work again now. svn path=/nixpkgs/trunk/; revision=826
2004-03-09 09:16:02 -08:00
stdenvs = (import ../../system/stdenvs.nix) {
* Finally we have a working stdenvLinux again. On the downside, the build process of stdenvLinux builds gcc 9 times (3 x 3 bootstrap stages). That's a bit excessive. svn path=/nixpkgs/trunk/; revision=880
2004-03-30 04:46:52 -08:00
inherit system;
* stdenv-nix-linux should more-or-less work again now. svn path=/nixpkgs/trunk/; revision=826
2004-03-09 09:16:02 -08:00
allPackages = import ../../system/all-packages-generic.nix;
* Started reorganising stdenv: - gcc/ld-wrappers have been factored out into a separate derivation. This allows a working gcc to be installed in the user environment. (Previously the Nix gcc didn't work because it needed a whole bunch of flags to point to glibc.) - Better modularity: packages can specify hooks into the setup scripts. For instance, setup no longer knows about the PKG_CONFIG_PATH variable; pkgconfig can set it up instead. - gcc not longer depends on binutils. This simplifies the bootstrap process. svn path=/nixpkgs/trunk/; revision=816
2004-03-08 08:02:46 -08:00
};
* Finally we have a working stdenvLinux again. On the downside, the build process of stdenvLinux builds gcc 9 times (3 x 3 bootstrap stages). That's a bit excessive. svn path=/nixpkgs/trunk/; revision=880
2004-03-30 04:46:52 -08:00
stdenv = stdenvs.stdenvNix;
* Started reorganising stdenv: - gcc/ld-wrappers have been factored out into a separate derivation. This allows a working gcc to be installed in the user environment. (Previously the Nix gcc didn't work because it needed a whole bunch of flags to point to glibc.) - Better modularity: packages can specify hooks into the setup scripts. For instance, setup no longer knows about the PKG_CONFIG_PATH variable; pkgconfig can set it up instead. - gcc not longer depends on binutils. This simplifies the bootstrap process. svn path=/nixpkgs/trunk/; revision=816
2004-03-08 08:02:46 -08:00
* Finally we have a working stdenvLinux again. On the downside, the build process of stdenvLinux builds gcc 9 times (3 x 3 bootstrap stages). That's a bit excessive. svn path=/nixpkgs/trunk/; revision=880
2004-03-30 04:46:52 -08:00
test = stdenv.mkDerivation {
* Started reorganising stdenv: - gcc/ld-wrappers have been factored out into a separate derivation. This allows a working gcc to be installed in the user environment. (Previously the Nix gcc didn't work because it needed a whole bunch of flags to point to glibc.) - Better modularity: packages can specify hooks into the setup scripts. For instance, setup no longer knows about the PKG_CONFIG_PATH variable; pkgconfig can set it up instead. - gcc not longer depends on binutils. This simplifies the bootstrap process. svn path=/nixpkgs/trunk/; revision=816
2004-03-08 08:02:46 -08:00
name = "simple-test";
builder = ./builder.sh;
};
body = test;
}