| Commit message (Collapse) | Author | Age |
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=22675
|
|
|
|
|
|
|
|
|
|
| |
If a build expressions has set "enableParallelBuilding = true", then the
generic builder may utilize more than one CPU core to build that particular
expression. This feature works out of the box for GNU Make. Expressions that
use other build drivers like Boost.Jam or SCons have to specify appropriate
flags such as "-j${NIX_BUILD_CORES}" themselves.
svn path=/nixpkgs/branches/stdenv-updates/; revision=22399
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=22336
|
|
|
|
|
|
| |
brought down the build farm
svn path=/nixpkgs/branches/stdenv-updates/; revision=22293
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=22283
|
|
|
|
|
|
|
|
| |
which prints a command before running it - add runMake which is using that function passing the makefile if set
make all make invokations use runMake
svn path=/nixpkgs/branches/stdenv-updates/; revision=22282
|
|
|
|
|
|
|
|
| |
but an up to date ppl package (because the current does not build with such a
new gmp)
svn path=/nixpkgs/branches/stdenv-updates/; revision=22267
|
|
|
|
|
|
|
| |
final stdenv gcc with ppl.
svn path=/nixpkgs/branches/stdenv-updates/; revision=22258
|
|\
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=21879
|
| |
| |
| |
| |
| |
| |
| | |
This reverts r21474 and r21467.
Also migrate wtk (r21472) to new API.
svn path=/nixpkgs/trunk/; revision=21575
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=21467
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=21292
|
|/
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=20454
|
|
|
|
|
|
| |
'null' elements.
svn path=/nixpkgs/trunk/; revision=20381
|
|
|
|
|
|
|
|
|
| |
"meta" and "passthru", and these attributes will be appended to the usual
mkDerivation attributes only if the package is cross built.
This allows putting some of the cross-building logic in the mkDerivation
nix parameters, and not only in the final builder script, as it was until now.
svn path=/nixpkgs/trunk/; revision=20272
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=19898
|
|
|
|
|
|
| |
the build farm.
svn path=/nixpkgs/trunk/; revision=19860
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=19815
|
|
|
|
|
|
| |
on OpenBSD
svn path=/nixpkgs/branches/stdenv-updates/; revision=19814
|
|
|
|
|
|
| |
on FreeBSD
svn path=/nixpkgs/branches/stdenv-updates/; revision=19795
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=19662
|
|
|
|
|
|
|
| |
* libpng updated to 1.4.0.
* For libjpegStatic, use a stdenv adapter to build a static library.
svn path=/nixpkgs/branches/stdenv-updates/; revision=19605
|
|
|
|
| |
svn path=/nixpkgs/branches/stdenv-updates/; revision=19536
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
I fixed conflicts regarding the renaming 'kernel' -> 'linux' in all-packages.
Also a small conflict in all-packages about making openssl overridable.
And I some linux 2.6.31-zen kernel files also marked in conflict.
svn path=/nixpkgs/branches/stdenv-updates/; revision=19438
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=19206
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=19028
|
|\|
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=18878
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=18667
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=18844
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
binutils,
we can't build easily with them gcc-4.4 natively, because of a bug in the ld of the
previous bootstrap-tools.
I updated the unpack script to include the new gcc-4.4 libraries *ppl*.so in patchelfing.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18835
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(dynamic libraries of ppl and cloogppl) into the package.
We need newer binutils in the bootstrap-tools for the armv5tel in order to
be able to build gcc 4.4 from them.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18747
|
| |
| |
| |
| |
| |
| |
| | |
updated the svn checkout published in http://nixos.org/tarballs/stdenv-linux/
svn path=/nixpkgs/branches/stdenv-updates/; revision=18700
|
| |
| |
| |
| |
| |
| |
| | |
installation.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18690
|
| |
| |
| |
| |
| |
| |
| | |
(required to build ppl with the bootstrap tools, when boostrapping gcc)
svn path=/nixpkgs/branches/stdenv-updates/; revision=18689
|
|\|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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=18651
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=18650
|
| |
| |
| |
| | |
svn path=/nixpkgs/trunk/; revision=18649
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
on a derivation with a meta.license attribute which does not satisfy the
license predicate.
With this adapter you can abort any install which depends on software
which are not free by default. You can try it with MPlayer, because
MPlayer depends of win32codecs flagged as "unfree".
svn path=/nixpkgs/trunk/; revision=18530
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
its dependencies. To make it works, you need to change the default
stdenv as documented in the error message.
./maintainers/scripts/dep-licenses.sh <attribute name>
svn path=/nixpkgs/trunk/; revision=18508
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=18579
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
this because 'ld' wants to know the path of every library involved in a dynamic
linking. I imagine that ld does not need that in native builds because it can
call the loader for it to resolve the library rpaths, but this is not the case
for cross-building.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18577
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
inputs did not get in)
Updating the xorg builder script to support cross building (in fact, support
for propagating the required build inputs).
svn path=/nixpkgs/branches/stdenv-updates/; revision=18569
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Disabling guile test, because one fails. I commented on that in the source.
On cross builds:
- Adding stripping
- Updating the glibc-2.11 expression to match the parameters of glibc-2.9,
which I was updating more.
- Renaming from selfNativeBuildInput to selfBuildNativeInput, so this matches
better the pattern buildNativeInputs.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18550
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Before this changes, cflags and ldflags for the native and the cross compiler
got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are
independant now, but enough, I think.
- Fixed the generic stdenv expression, which did a big mess on buildInputs and
buildNativeInputs. Now it distinguishes when there is a stdenvCross or not.
Maybe we should have a single stdenv and forget about the stdenvCross
adapter - this could end in a stdenv a bit complex, but simpler than the
generic stdenv + adapter.
- Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH
now works for both the cross and the native compilers, but I think this
should work well for most cases I can think of.
- I tried to fix the guile expression to cross-biuld; guile is built, but not
its manual, so the derivation still fails. Guile requires patching to
cross-build, as far as I understnad.
- Made the glibcCross build to be done through the usage of a
gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it
directly.
- Trying to make physfs (a neverball dependency) cross build.
- Updated the gcc expression to support building a cross compiler without getting
derivation variables mixed with those of the stdenvCross.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
|
| |
| |
| |
| | |
svn path=/nixpkgs/branches/stdenv-updates/; revision=18492
|
| |
| |
| |
| |
| |
| |
| |
| | |
statement of the gcc-wrapper coreutils dependency on r17867.
I don't have i686-darwin to try this.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18490
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
true/false, which tells whether the derivation needs itself as
buildNativeInput.
For example, in order to build cross ncurses, we need the a native build
ncurses.
(As libtool does not work in stdenv, I have not tested this change, to check
whether finally ncurses cross-build)
svn path=/nixpkgs/branches/stdenv-updates/; revision=18489
|
| |
| |
| |
| |
| |
| |
| | |
I don't know why there are such calls, but there are.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18482
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
derivation, the "buildInputs" in every stdenv mkDerivation don't map now
directly to the environment
variable "buildInputs" in the builder, but "buildNativeInputs". So, the inputs
build by the native compiler.
When cross compiling, they will map to the environment variable "buildInputs"
(yes, now the same name), which means does to be built with the cross compiler.
I think I improved the naming of variables a bit. There was a big mess,
specially in the stdenv adapter for cross building, and also in the default
builder script.
I also tried to add proper manager of propagatedInputBuilds, these being
propagated considering the host or build origin of that input build (so, at the
end, being those propagatedInputBuilds being propagated properly to the native
or the cross compiler.
svn path=/nixpkgs/branches/stdenv-updates/; revision=18477
|