Third go at renaming patches to contain neither the package name nor the package version.
1 [ Building gcc-2.95.3 on cygwin yields a compiler that sticks a .exe
2 on the end of every executable, even if they're linux executable.
3 This is highly annoying, and causes glibc build failures that look like this:
4 mv: `.../bin/makedb.new' and `.../bin/makedb' are the same file
5 make[2]: *** [.../bin/makedb] Error 1
6 make[2]: Leaving directory `.../gcc-2.95.3-glibc-2.1.3/glibc-2.1.3/db2'
8 The mainline solves this with http://gcc.gnu.org/ml/gcc-cvs/2001-04/msg00440.html,
9 but that doesn't apply cleanly to gcc-2.95.3.
12 http://www.uclinux.org/pub/uClinux/uclinux-elf-tools/tools-20030314/gcc-2.95.3-cygwin-020611.patch
13 This is the only patch in crosstool that *isn't* suitable for the mainline.
14 I can live with this patch simply because crosstool does not build
15 compilers that target cygwin or VAX/VMS.
16 If that ever changes, I might need to try applying the real patch.
22 # This patch can be found at http://www.uclinux.org/pub/uClinux/m68k-elf-tools/
24 --- gcc-2.95.3/gcc/config/i386/xm-cygwin.h 1999-04-22 16:40:56.000000000 +0200
25 +++ gcc-2.95.3-cygwin/gcc/config/i386/xm-cygwin.h 2002-06-11 08:23:18.000000000 +0200
27 the Free Software Foundation, 59 Temple Place - Suite 330,
28 Boston, MA 02111-1307, USA. */
30 -#define EXECUTABLE_SUFFIX ".exe"
31 #define NO_SYS_SIGLIST 1
33 /* We support both "/" and "\" since everybody tests both but we