'.exe' in output file
Tue Sep 3 17:22:00 GMT 2002
OK, looks like patches to fix this have been posted several times:
They appear to have gone into the gcc tree Apr 19 2001:
The release I was using, gcc3.0.x, was last updated in Feb 2001.
Thus gcc3.1 probably has the bug fixed.
I managed to apply the March patch to my gcc3.0.2 tree, and am now building...
> Yeah, we gathered something like that would work, but
> we can't figure out why that is having any effect on
> a cross-compiler. Shouldn't that only affect a native
> cygwin compiler, not one that targets linux?
> It'd be cool to find the real fix.
> - Dan
> Sangmoon Kim wrote:
>> Just comment out the EXECUTABLE_SUFFIX macro in
>> gcc/config/i386/xm-cygwin.h and rebuild gcc.
>> ----- Original Message -----
>> From: "Xiao Shi" <firstname.lastname@example.org>
>> To: <email@example.com>
>> Sent: Wednesday, August 28, 2002 3:15 AM
>> Subject: '.exe' in output file
>> > Hi:
>> > I am building a cross compiler for power pc 750 on cygwin. But by using
>> > the -o option in gcc, the executable file will always have a '.exe' append
>> > to it. Does anyone know how I can get rid of it?
>> > I already know that '.exe' is caused by gcc/config.gcc when it was ran by
>> > configure. My configure line looks like this ../gcc-3.0.2/configure
>> > --target=powerpc-linux --host=i686-pc-cygwin --build=$BUILD=i686-pc-cygwin
>> > --prefix=/opt/hardhat/devkit/ppc/7xx
>> > --with-headers=/opt/hardhat/devkit/ppc/7xx/target/usr/include
>> > --enable-shared --enable-long-long --enable-threads=posix
>> > --enable-langugages=c,c++ -enable-cxx-flags="" --with-cpu=750. Should I
>> > include another --option. Thanks
>> > Kent Shi
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to firstname.lastname@example.org
More information about the crossgcc