Re: [bryan.richter-Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org: Fwd: Compile error under cygwin]

On 2008-01-03, Tuomo Valkonen <[email protected]> wrote:
> That's just utterly and totally brain-dead. If I say '-o ion3', 
> then that's where the output should go, even if the rest of the
> system can't handle the lack of a lame extension. I wonder if 
> they have a modified variant of install-sh or so, that can 
> handle the way they've fucked up gcc? 

By googling around a bit, I found this:

> The Cygwin stat(), lstat() and readlink() functions make the .exe extension
> transparent by looking for foo.exe when you ask for foo (unless a foo also
> exists). Cygwin does not require a .exe extension, but gcc adds it
> automatically when building a program. However, when accessing an executable
> as a normal file (e.g., cp in a makefile) the .exe is not transparent. The
> install included with Cygwin automatically appends a .exe when necessary.
(http://www.ayni.com/perldoc/perl5.8.0/README.cygwin.html)

So it's not even cygwin itself that's brain-dead, but gcc itself (typical!)
and, indeed, cygwin provides a hacked version of install. Just replacing the
provided install-sh in the INSTALL setting with cygwin's install, should do
the job. (The provided install-sh script instead of the system's install
command is used by default, because there are incompatible versions of
install.)

-- 
Tuomo