[Nix-dev] Re: [Nix-commits] SVN commit: nix - 18833 - viric - in nixpkgs/branches/stdenv-updates/pkgs: development/compilers/gcc-4.3 development/compilers/gcc-4.4 top-level

[Ludovic Courtès]

Hi,

Llus Batlle <viriketo at gmail.com> writes:

> --- nixpkgs/branches/stdenv-updates/pkgs/development/compilers/gcc-4.4/libtool-glibc.patch	                        (rev 0)
> +++ nixpkgs/branches/stdenv-updates/pkgs/development/compilers/gcc-4.4/libtool-glibc.patch	2009-12-08 09:36:19 UTC (rev 18833)
> @@ -0,0 +1,48 @@
> +diff --git a/libgomp/configure b/libgomp/configure
> +index deef673..9e4a790 100755
> +--- a/libgomp/configure
> ++++ b/libgomp/configure
> +@@ -23848,6 +23848,11 @@ old_archive_cmds=$lt_old_archive_cmds
> + # A language specific compiler.
> + CC=$lt_compiler
> + 
> ++# Ugly hack to get libmudflap (and other libraries) to build.
> ++# Libtool filters out \`-B' flags when linking (why?), so the \`-B' flag
> ++# to Glibc gets lost.  Here we forcibly add it to any invocation.
> ++CC="\$CC $NIX_EXTRA_CFLAGS_TARGET $NIX_EXTRA_LDFLAGS_TARGET"
> ++

We’ve already discussed that elsewhere, but having cleaned the gcc 4.4
expression from such nix-specific kludges, I was really hoping they
would not come back a few months later.  ;-)

I understand using $LIBRARY_PATH and $CPATH was somehow causing you
troubles for building a cross-compiler (or was it cross-compiling a
compiler?), but still, I think we should strive to use the standard
build system as much as we can so that it’s maintainable,
understandable, etc.

I’m not offering any fix here, as I don’t want to spend time working on
cross-compilation, but I’d really love it if we could sit back and make
sure no kosher way exists to achieve what we want.

Can you please re-send the GCC bug reports you made and perhaps a
summary of the approaches you tried?

Thanks,
Ludo’.