Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: "Andre Oliveira da Costa" To: "Cygwin" Subject: Handling of .exe filenames Date: Tue, 21 Dec 1999 10:22:37 -0200 Message-ID: <000001bf4bae$10efd8d0$8400000a@costa.cadenet.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Hi, the linker distributed with cygwin creates .exe files by default (i.e. we don't have to put "-o filename.exe" in our makefiles). "ls" also does this "translation": for example ls -l /usr/local/bin/vim and ls -l /usr/local/bin/vim.exe produce the same results. I was wondering why other tools like strip don't behave the same. If they did, makefiles created for UNIX would be more easily ported to cygwin. I'm saying this because the programs I compile directly from source on cygwin usually break during the install phase, because either "strip", "cp" or "install" complains that it can't find "filename" (without the .exe extension). I understand it goes against UNIX behavior to treat a file differently according to its extension, and I totally agree with that. But, since we are on this bizarre Micro$oft world, and "ld" and "ls" have this special handling of executable binaries, shouldn't this behavior be extended to other utilities as well? Regards, Andre -- André Oliveira da Costa (costa AT cade DOT com DOT br) -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com