summary refs log tree commit diff
path: root/pkgs/build-support
diff options
context:
space:
mode:
authorEelco Dolstra <eelco.dolstra@logicblox.com>2006-10-26 20:25:31 +0000
committerEelco Dolstra <eelco.dolstra@logicblox.com>2006-10-26 20:25:31 +0000
commitc8cc99203894c2464a7961b5e6bd8a46a25ed2d6 (patch)
tree6613f9a4097db607b53c23c6ea5772b07591b54f /pkgs/build-support
parent2d3cfb2058edac6f95997ed7dbce6dc1d0e17f78 (diff)
downloadnixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar.gz
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar.bz2
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar.lz
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar.xz
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.tar.zst
nixlib-c8cc99203894c2464a7961b5e6bd8a46a25ed2d6.zip
* Put a symlink to the assembler in the GCC wrapper. Otherwise, when
  we use the GCC wrapper in a user environment, the wrong assembler
  will be called.  This is not usually a problem, but sometimes it is
  (e.g., when using G++ 4.1.1 with binutils 2.16 or so).

svn path=/nixpkgs/trunk/; revision=6862
Diffstat (limited to 'pkgs/build-support')
-rw-r--r--pkgs/build-support/gcc-wrapper/builder.sh6
1 files changed, 6 insertions, 0 deletions
diff --git a/pkgs/build-support/gcc-wrapper/builder.sh b/pkgs/build-support/gcc-wrapper/builder.sh
index 20e15405526f..e0f880d8df6f 100644
--- a/pkgs/build-support/gcc-wrapper/builder.sh
+++ b/pkgs/build-support/gcc-wrapper/builder.sh
@@ -89,6 +89,12 @@ mkGccWrapper $out/bin/g77 $gccPath/g77
 ln -s g77 $out/bin/f77
 
 
+# Create a symlink to as (the assembler).  This is useful when a
+# gcc-wrapper is installed in a user environment, as it ensures that
+# the right assembler is called.
+ln -s $nativePrefix/bin/as $out/bin/as
+
+
 # Make a wrapper around the linker.
 doSubstitute "$ldWrapper" "$out/bin/ld"
 chmod +x "$out/bin/ld"