This is the mail archive of the
mailing list for the Cygwin project.
Re: Tracing down problem when compiling GCC 3.3 under cygwin PR 10626
On Tue, May 06, 2003 at 07:48:07PM +0200, ?yvind Harboe wrote:
>I am experiencing an intermittant problem when compiling GCC 3.3
>When I reported it to the GCC guys, I was asked to elaborate
>but my CygWin/Linux skills are too limited to be of much help.
>Basically there is a GCC script "install-sh" that fails intermittantely
>Please find more information in GCC bug-report.
>Here is a bit more information that probably illustrates the problems
>install-sh is running into under CygWin:
>Session from CygWin shell. "cp" understands the ".exe" extensions,
>but "mv" gets confused.
>arm armscripts ecos gcc-install.log gcc33 mingw
>armgdb32 armsize foobar.exe gcc-make.log gdbtk.ini scripts
>$ mv foobar barfoo
>mv: preserving times for `barfoo': No such file or directory
>mv: preserving ownership for `barfoo': No such file or directory
>mv: cannot unlink `foobar': No such file or directory
>mv: cannot remove `foobar': No such file or directory
>$ cp foobar barfoo
State-Changed-When: Tue May 6 10:59:02 2003
> Would you please elaborate on how this is a GCC bug?
> It looks more like a Cygwin bug to me...
AFAICT, install-sh should never be asked to install an executable which
lacks an .exe when the executable was built with a .exe extension. So,
the fact that sometimes it "works" is a red herring. As you noted, cp
has limited support for copying .exe files and mv has none. It really
is up to gcc to accommodate that by specifying the .exe extension in all
cases. That's the whole point of having an install-sh script. It's
supposed to be accommodating of system pecularities.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html