| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
It's currently the same machine, but tarballs.nixos.org should become
an S3/CloudFront site eventually.
|
|
|
|
|
|
|
| |
Due to xz being override in the last stdenv and also in the previous, the
nixpkgs xz ended up being built by bootstrap-tools, and thus depending on it
through libgcc_so.so.1. That ends up making 'nix' with a runtime
dependency on bootstrap-tools.
|
|\
| |
| |
| |
| |
| | |
This adds raspberry pi support. I've almost tested all.
Should fix https://github.com/NixOS/nixpkgs/issues/234
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Although patching it made some programs run (configure tests), some others
crashed with segfault. So I don't think there is any win patching it. The
proper way to solve the bootstrap in the raspberry pi is, as far as I've been
testing, use glibc 2.17 libs in bootstrap-tools with the same ld.so name as the
bootstrapped glibc.
This is a problem inherent in our way to bootstrap, that first replaces
the glibc of a given gcc+glibc (bootstrap-tools) with gcc-wrapper tricks, and
then builds a new gcc. A nicer way would be to build a gcc without glibc,
then the glibc, then the final gcc, as we do with cross-tools.
Some comments about this problem in
https://github.com/NixOS/nixpkgs/issues/234#issuecomment-11764352
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This solves the problem of the change of name in ld.so between
glibc 2.13 and 2.17 (at least for armhf). Some comments about it in
https://github.com/NixOS/nixpkgs/issues/234#issuecomment-11764352
As there says, without this, gmp (after glibc built) tests crashed
- segfault.
|
| |
| |
| |
| |
| | |
I also move the 'echo patching' lines down, so they are printed
only for files really patched.
|
| |
| |
| |
| | |
Out of glibc libs, only libstdc++ requires ld.so.
|
| |
| |
| |
| |
| |
| | |
libstdc++ and libmudflapth link to the dynamic loader; if the
bootstrap uses another dynamic loader name, and the rpath of these
libs isn't changed, they will fail to load.
|
| |
| |
| |
| | |
Trying again to get a hardfp compiler.
|
| | |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
pkgs/development/compilers/gcc/4.6/default.nix
pkgs/development/compilers/gcc/4.7/default.nix
The 4.7 had some weird parameters added in crossAttrs; I've removed
them, but I don't understand where they come from.
|
| | |
| | |
| | |
| | | |
It doesn't reference <nixpkgs> anymore. And I fixed the indentation.
|
| | |
| | |
| | |
| | |
| | |
| | | |
I had those changes from the time when I wanted to bootstrap
its stdenvLinux from armv5tel bootstrap-tools. But that
never worked.
|
| |\ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
I had lost this change in some branch.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Based on the cross/make-bootstrap-tools.nix I had for the sheevaplug
in my nixos.org svn configuration directory.
|
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
Now that we have a way to alter /bin/sh in chroots on non-NixOS Linux
platforms, it may be useful to have access to stdenv.shell package and to
static bash contained in bootstrap tools. So make them accessible via stdenv
attribute set.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows various applications. It allows users to set global
optimisation flags, e.g.
stdenv.userHook = ''NIX_CFLAGS_COMPILE+=" -funroll-loops"'';
But the impetus is as an alternative to issue #229, allowing impure
stdenv setup for people who want to use distcc:
stdenv.userHook = "source /my/impure/setup-script.sh";
This is probably a bad idea, but at least now it's a bad idea in
people's configuration and not in Nixpkgs. :-)
|
| |/
|/|
| |
| |
| | |
This reverts commit e04b17bfbaa4dbd5252d59f727d7d84ffe25f568, reversing
changes made to 1af2ada7d4c61e79356a0f3f8bcced6159a6e751.
|
| | |
|
|/ |
|
|
|
|
| |
I make the nix expression point to them.
|
|
|
|
| |
It'd be nice having this in nixos.org though.
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=33798
|
|\
| |
| |
| |
| |
| | |
Conflicts: cups, all-packages.nix (gcc45_debug)
svn path=/nixpkgs/branches/stdenv-updates/; revision=31863
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
what the new nix thinks the fuloong is.
Anyone having the old nix should use a nixpkgs previous to this change to build
the new nix. And then, with the new nix, he can use any newer nixpkgs revision.
svn path=/nixpkgs/trunk/; revision=31751
|
| |
| |
| |
| |
| |
| | |
so that "nix-env -i stdenv" does the expected.
svn path=/nixpkgs/branches/stdenv-updates/; revision=31742
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=31734
|
| |
| |
| |
| |
| |
| | |
* Don't call xargs with the -r flag in the Darwin bootstrap.
svn path=/nixpkgs/branches/stdenv-updates/; revision=31703
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=31700
|
| |
| |
| |
| |
| |
| |
| | |
bash's pattern replacement feature. "replace-literal" is an
uncommon command so it was a headache during the bootstrap.
svn path=/nixpkgs/branches/stdenv-updates/; revision=31681
|
| |
| |
| |
| |
| |
| | |
function, so obsolete it.
svn path=/nixpkgs/branches/stdenv-updates/; revision=31644
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
some redundant builds (e.g., GMP was built three times).
* Updated GMP to 5.0.2.
* Updated PPL to 0.11.2.
* Remove ad hoc flags to build GCC's dependencies statically.
Instead, use the ‘makeStaticLibraries’ stdenv adapter.
* Build GMP with C++ support by default.
svn path=/nixpkgs/branches/stdenv-updates/; revision=30891
|
| |
| |
| |
| |
| |
| | |
in its interaction with the ‘dontStrip’ attribute.
svn path=/nixpkgs/branches/stdenv-updates/; revision=30848
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=29847
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=28958
|
|\|
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=28792
|
| |
| |
| |
| |
| |
| |
| |
| | |
passthrough capabilities.
I may test to see if stdenv can be built without these features (I see no reason why not)
svn path=/nixpkgs/trunk/; revision=26698
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=26696
|
|/
|
|
| |
svn path=/nixpkgs/branches/modular-python/; revision=26680
|