2008-07-08 01:11:53 +02:00
|
|
|
{ stdenv, fetchurl, kernelHeaders
|
|
|
|
, installLocales ? true
|
|
|
|
, profilingLibraries ? false
|
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
|
|
|
, gccCross ? null
|
2008-07-08 01:11:53 +02:00
|
|
|
}:
|
Big fixes in the cross build:
- 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
2009-11-22 20:51:45 +01:00
|
|
|
let
|
|
|
|
cross = if gccCross != null then gccCross.target else null;
|
|
|
|
in
|
2008-10-07 18:55:20 +02:00
|
|
|
stdenv.mkDerivation rec {
|
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
|
|
|
name = "glibc-2.9" +
|
2009-11-17 00:21:13 +01:00
|
|
|
stdenv.lib.optionalString (cross != null) "-${cross.config}";
|
2009-06-24 22:10:59 +02:00
|
|
|
|
2008-07-08 01:11:53 +02:00
|
|
|
builder = ./builder.sh;
|
2009-06-24 22:10:59 +02:00
|
|
|
|
2008-10-07 18:55:20 +02:00
|
|
|
src = fetchurl {
|
2009-11-08 01:32:12 +01:00
|
|
|
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";
|
2008-07-08 01:11:53 +02:00
|
|
|
};
|
|
|
|
|
2009-11-17 00:21:13 +01:00
|
|
|
inherit kernelHeaders installLocales;
|
|
|
|
crossConfig = if (cross != null) then cross.config else null;
|
2008-07-08 01:11:53 +02:00
|
|
|
|
|
|
|
inherit (stdenv) is64bit;
|
|
|
|
|
|
|
|
patches = [
|
|
|
|
/* Fix for NIXPKGS-79: when doing host name lookups, when
|
|
|
|
nsswitch.conf contains a line like
|
|
|
|
|
|
|
|
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
|
|
|
|
|
|
|
|
don't return an error when mdns4_minimal can't be found. This
|
|
|
|
is a bug in Glibc: when a service can't be found, NSS should
|
|
|
|
continue to the next service unless "UNAVAIL=return" is set.
|
|
|
|
("NOTFOUND=return" refers to the service returning a NOTFOUND
|
|
|
|
error, not the service itself not being found.) The reason is
|
|
|
|
that the "status" variable (while initialised to UNAVAIL) is
|
|
|
|
outside of the loop that iterates over the services, the
|
|
|
|
"files" service sets status to NOTFOUND. So when the call to
|
|
|
|
find "mdns4_minimal" fails, "status" will still be NOTFOUND,
|
|
|
|
and it will return instead of continuing to "dns". Thus, the
|
|
|
|
line
|
|
|
|
|
|
|
|
hosts: mdns4_minimal [NOTFOUND=return] dns mdns4
|
|
|
|
|
|
|
|
does work because "status" will contain UNAVAIL after the
|
|
|
|
failure to find mdns4_minimal. */
|
|
|
|
./nss-skip-unavail.patch
|
2009-04-19 17:28:37 +02:00
|
|
|
|
|
|
|
/* Make it possible to override the locale-archive in NixOS. */
|
2009-04-19 18:07:00 +02:00
|
|
|
./locale-override.patch
|
2009-04-22 14:55:47 +02:00
|
|
|
|
|
|
|
/* Have rpcgen(1) look for cpp(1) in $PATH. */
|
|
|
|
./rpcgen-path.patch
|
2009-11-08 01:32:12 +01:00
|
|
|
|
|
|
|
/* Support GNU Binutils 2.20 and above. */
|
|
|
|
./binutils-2.20.patch
|
2009-11-15 06:28:35 +01:00
|
|
|
|
|
|
|
./binutils-ld.patch
|
2008-07-08 01:11:53 +02:00
|
|
|
];
|
|
|
|
|
2009-11-08 01:32:12 +01:00
|
|
|
configureFlags = [
|
|
|
|
"--enable-add-ons"
|
|
|
|
"--with-headers=${kernelHeaders}/include"
|
|
|
|
(if profilingLibraries then "--enable-profile" else "--disable-profile")
|
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.lib.optionals (cross != null) [
|
2009-11-15 06:28:35 +01:00
|
|
|
"--with-tls"
|
|
|
|
"--enable-kernel=2.6.0"
|
|
|
|
"--without-fp"
|
|
|
|
"--with-__thread"
|
2009-11-08 01:32:12 +01:00
|
|
|
] ++ (if (stdenv.system == "armv5tel-linux") then [
|
|
|
|
"--host=arm-linux-gnueabi"
|
|
|
|
"--build=arm-linux-gnueabi"
|
|
|
|
"--without-fp"
|
|
|
|
] else []);
|
|
|
|
|
Big fixes in the cross build:
- 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
2009-11-22 20:51:45 +01:00
|
|
|
buildNativeInputs = stdenv.lib.optionals (cross != null) [ gccCross ];
|
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
|
|
|
|
2009-11-23 18:06:57 +01:00
|
|
|
preInstall = if (cross != null) then ''
|
2012-01-18 21:16:00 +01:00
|
|
|
mkdir -p $out/lib
|
2009-11-08 01:32:12 +01:00
|
|
|
ln -s ${stdenv.gcc.gcc}/lib/libgcc_s.so.1 $out/lib/libgcc_s.so.1
|
2009-11-23 18:06:57 +01:00
|
|
|
'' else "";
|
2009-11-08 01:32:12 +01:00
|
|
|
|
2009-11-23 18:06:57 +01:00
|
|
|
postInstall = if (cross != null) then ''
|
2009-11-08 01:32:12 +01:00
|
|
|
rm $out/lib/libgcc_s.so.1
|
2009-11-23 18:06:57 +01:00
|
|
|
'' else "";
|
2008-07-08 01:11:53 +02:00
|
|
|
|
|
|
|
# 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";
|
2008-10-07 18:55:20 +02:00
|
|
|
|
|
|
|
meta = {
|
|
|
|
homepage = http://www.gnu.org/software/libc/;
|
|
|
|
description = "The GNU C Library";
|
|
|
|
};
|
2008-07-08 01:11:53 +02:00
|
|
|
}
|