nixpkgs/pkgs/build-support/gcc-wrapper
Eelco Dolstra c8cc992038 * 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
2006-10-26 20:25:31 +00:00
..
add-flags * Add -B$gcc/lib64 when appropriate. This is so that configure 2006-10-25 16:32:13 +00:00
builder.sh * Put a symlink to the assembler in the GCC wrapper. Otherwise, when 2006-10-26 20:25:31 +00:00
default.nix * gcc-wrapper: separately store the flags necessary to find GCC and 2006-10-24 18:26:23 +00:00
gcc-wrapper.sh * gcc-wrapper: separately store the flags necessary to find GCC and 2006-10-24 18:26:23 +00:00
ld-wrapper.sh * gcc-wrapper: separately store the flags necessary to find GCC and 2006-10-24 18:26:23 +00:00
setup-hook.sh * gcc-wrapper: separately store the flags necessary to find GCC and 2006-10-24 18:26:23 +00:00
utils.sh * Accept relative paths such as -I ..' (-I..' was already being 2004-04-07 14:15:54 +00:00