My first attempt at getting cross compilers in nixpkgs.
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
2009-11-14 09:11:30 +01:00
|
|
|
{ stdenv, fetchurl, kernelHeaders
|
|
|
|
|
, profilingLibraries ? false
|
|
|
|
|
}:
|
|
|
|
|
|
|
|
|
|
stdenv.mkDerivation rec {
|
|
|
|
|
name = "glibc-headers-2.9";
|
|
|
|
|
|
|
|
|
|
builder = ./headersbuilder.sh;
|
|
|
|
|
|
|
|
|
|
src = fetchurl {
|
|
|
|
|
url = http://ftp.gnu.org/gnu/glibc/glibc-2.9.tar.bz2;
|
|
|
|
|
sha256 = "0v53m7flx6qcx7cvrvvw6a4dx4x3y6k8nvpc4wfv5xaaqy2am2q9";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
srcPorts = fetchurl {
|
|
|
|
|
url = http://ftp.gnu.org/gnu/glibc/glibc-ports-2.9.tar.bz2;
|
|
|
|
|
sha256 = "0r2sn527wxqifi63di7ns9wbjh1cainxn978w178khhy7yw9fk42";
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
inherit kernelHeaders;
|
|
|
|
|
|
|
|
|
|
inherit (stdenv) is64bit;
|
|
|
|
|
|
|
|
|
|
patches = [
|
|
|
|
|
/* Support GNU Binutils 2.20 and above. */
|
|
|
|
|
./binutils-2.20.patch
|
|
|
|
|
];
|
|
|
|
|
|
|
|
|
|
configureFlags = [
|
|
|
|
|
"--enable-add-ons"
|
|
|
|
|
"--with-headers=${kernelHeaders}/include"
|
|
|
|
|
"--disable-sanity-checks"
|
|
|
|
|
"--enable-hacker-mode"
|
|
|
|
|
(if profilingLibraries then "--enable-profile" else "--disable-profile")
|
2012-04-16 01:41:25 +02:00
|
|
|
] ++ (if stdenv.isArm then [
|
My first attempt at getting cross compilers in nixpkgs.
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
2009-11-14 09:11:30 +01:00
|
|
|
"--host=arm-linux-gnueabi"
|
|
|
|
|
"--build=arm-linux-gnueabi"
|
|
|
|
|
"--without-fp"
|
|
|
|
|
] else []);
|
|
|
|
|
|
|
|
|
|
buildPhase = "true";
|
|
|
|
|
|
|
|
|
|
# I took some tricks from crosstool-0.43
|
|
|
|
|
installPhase = ''
|
|
|
|
|
make cross-compiling=yes CFLAGS=-DBOOTSTRAP_GCC install-headers
|
|
|
|
|
mkdir -p $out/include/gnu
|
|
|
|
|
touch $out/include/gnu/stubs.h
|
|
|
|
|
cp ../include/features.h $out/include/features.h
|
|
|
|
|
(cd $out/include && ln -s $kernelHeaders/include/* .) || exit 1
|
|
|
|
|
'';
|
|
|
|
|
|
|
|
|
|
# Workaround for this bug:
|
|
|
|
|
# http://sourceware.org/bugzilla/show_bug.cgi?id=411
|
|
|
|
|
# I.e. when gcc is compiled with --with-arch=i686, then the
|
|
|
|
|
# preprocessor symbol `__i686' will be defined to `1'. This causes
|
|
|
|
|
# the symbol __i686.get_pc_thunk.dx to be mangled.
|
|
|
|
|
NIX_CFLAGS_COMPILE = "-U__i686";
|
|
|
|
|
|
|
|
|
|
meta = {
|
|
|
|
|
homepage = http://www.gnu.org/software/libc/;
|
|
|
|
|
description = "The GNU C Library";
|
|
|
|
|
};
|
|
|
|
|
}
|