1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/patches/gcc/2.95.3/150-cygwin-020611.patch	Mon Jul 28 21:08:01 2008 +0000
     1.3 @@ -0,0 +1,33 @@
     1.4 +[ Building gcc-2.95.3 on cygwin yields a compiler that sticks a .exe
     1.5 +  on the end of every executable, even if they're linux executable.
     1.6 +  This is highly annoying, and causes glibc build failures that look like this:
     1.7 +    mv: `.../bin/makedb.new' and `.../bin/makedb' are the same file
     1.8 +    make[2]: *** [.../bin/makedb] Error 1
     1.9 +    make[2]: Leaving directory `.../gcc-2.95.3-glibc-2.1.3/glibc-2.1.3/db2'
    1.10 +
    1.11 +  The mainline solves this with http://gcc.gnu.org/ml/gcc-cvs/2001-04/msg00440.html,
    1.12 +  but that doesn't apply cleanly to gcc-2.95.3.
    1.13 +
    1.14 +  So, I'm using
    1.15 +  http://www.uclinux.org/pub/uClinux/uclinux-elf-tools/tools-20030314/gcc-2.95.3-cygwin-020611.patch
    1.16 +  This is the only patch in crosstool that *isn't* suitable for the mainline.
    1.17 +  I can live with this patch simply because crosstool does not build
    1.18 +  compilers that target cygwin or VAX/VMS. 
    1.19 +  If that ever changes, I might need to try applying the real patch.
    1.20 +]
    1.21 +
    1.22 +
    1.23 +
    1.24 +#
    1.25 +# This patch can be found at http://www.uclinux.org/pub/uClinux/m68k-elf-tools/
    1.26 +#
    1.27 +--- gcc-2.95.3/gcc/config/i386/xm-cygwin.h	1999-04-22 16:40:56.000000000 +0200
    1.28 ++++ gcc-2.95.3-cygwin/gcc/config/i386/xm-cygwin.h	2002-06-11 08:23:18.000000000 +0200
    1.29 +@@ -19,7 +19,6 @@
    1.30 + the Free Software Foundation, 59 Temple Place - Suite 330,
    1.31 + Boston, MA 02111-1307, USA. */
    1.32 + 
    1.33 +-#define EXECUTABLE_SUFFIX ".exe"
    1.34 + #define NO_SYS_SIGLIST 1
    1.35 + 
    1.36 + /* We support both "/" and "\" since everybody tests both but we