| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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. :-)
|
|/ |
|
| |
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=33798
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'mips64-linux'.
(my git-svn info:)
Merge branch 'mips64' into stdenv-updates
Conflicts:
pkgs/applications/networking/browsers/firefox/3.6.nix
pkgs/top-level/all-packages.nix
svn path=/nixpkgs/branches/stdenv-updates/; revision=23588
|
|
|
|
|
|
| |
so it can be used in places like the linuxHeaders expression.
svn path=/nixpkgs/branches/stdenv-updates/; revision=23343
|
|
|
|
|
|
| |
(boostrap-files cross-built)
svn path=/nixpkgs/branches/stdenv-updates/; revision=22849
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
renaming.
I think directory renaming breaks the usual merges... because it leaves the
'to be removed' directory in the working directory still. A manual 'rm' of the
'to be removed' directory fixed the commit.
svn merge ^/nixpkgs/trunk
svn path=/nixpkgs/branches/stdenv-updates/; revision=18661
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=18649
|
| |
| |
| |
| |
| |
| |
| | |
into a stdenv adapater.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18397
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
My idea is to provide special stdenv expressions that will contain in the path
additional cross compilers. As most expressions for programs accept a stdenv parameter,
we could substitute this parameter with the special stdenv, which will have a
generic builder that attempts the usual "--target=..." and can additionally
have an env variable like "cross" with the target architecture set.
So, finally we could have additional expressions like this:
bashRealArm = makeOverridable (import ../shells/bash) {
inherit fetchurl bison;
stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi";
};
Meanwhile it does not work - I still cannot get the cross-gcc to build.
I think it does not fill the previous expressions with a lot of noise, so I
think it may be a good path to follow.
I only touched some files of the current stdenv: gcc-4.3, kernel headers
2.6.28, glibc 2.9, ...
I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will
update it, or update the gcc-wrapper expression to make it fit the cross tools,
but meanwhile I even cannot build gcc, so I have not tested the wrapper.
This new idea on cross compiling is not similar to that of the
nixpkgs/branches/cross-compilation, which mostly added bare new expressions for
anything to be cross compiled, if I understood it correctly.
I cared not to break anything of the usual stdenv in all this work.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This comes from:
svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff
patch -p0 < diff
and then adding into svn all files new from the patch.
trunk@18255 comes from the last time I updated stdenv-updates from trunk.
svn path=/nixpkgs/stdenv-updates2/; revision=18272
|
|
|
|
|
|
|
|
|
| |
I thought I didn't change stdenv, but I did. This will go soon into the stdenv
branch then.
Reverse-merging r16467 through r16465.
svn path=/nixpkgs/trunk/; revision=16468
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=16466
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=13968
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=13957
|
|
|
|
|
|
| |
stdenv.
svn path=/nixpkgs/trunk/; revision=12147
|
|
|
|
|
|
| |
stdenv/nix.
svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10812
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6899
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6867
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6849
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6828
|
|
|
|
|
|
|
| |
"i686-cygwin") by adding an argument "stdenvType" to specify which
stdenv to use (like "i686-mingw").
svn path=/nixpkgs/trunk/; revision=6213
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6123
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=6122
|
|
|
|
|
|
| |
external binutils (i.e., Apple's cctools in /usr/bin).
svn path=/nixpkgs/trunk/; revision=5706
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=5702
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=5597
|
|
|
|
|
|
| |
with the lack of an RPATH.
svn path=/nixpkgs/trunk/; revision=5362
|
|
svn path=/nixpkgs/branches/usability/; revision=4774
|