public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] make install installs executables without .exe extension
Date: Mon, 19 Jan 2009 15:51:00 -0000	[thread overview]
Message-ID: <7zsknf2t7b.fsf@vzell-de.de.oracle.com> (raw)
In-Reply-To: <496EAFE3.2040707@byu.net> (Eric Blake's message of "Wed, 	14 Jan 2009 20:39:15 -0700")

>>>>> Eric Blake writes:

    > According to Dr. Volker Zell on 1/14/2009 4:38 PM:
    >> Hi
    >> 
    >> I'm about to recompile my packages under cygwin 1.7 and just noticed
    >> that although the compiler creates executables with .exe extensions the
    >> extension is somehow stripped after make install step.
    >> 
    >> Any hints ?

    > Might be something wrong with my .exe magic patch in coreutils.  I'll look
    > into it.

Under cygwin 1.5

when filename.exe exists

/usr/bin/install filename /tmp            creates /tmp/filename.exe
/usr/bin/cp      filename /tmp            creates /tmp/filename.exe
/usr/bin/install filename /tmp/filename   creates /tmp/filename.exe
/usr/bin/cp      filename /tmp/filename   creates /tmp/filename.exe

Under cygwin 1.7

when filename.exe exists

/usr/bin/install filename /tmp            creates /tmp/filename
/usr/bin/cp      filename /tmp            creates /tmp/filename
/usr/bin/install filename /tmp/filename   creates /tmp/filename
/usr/bin/cp      filename /tmp/filename   creates /tmp/filename

Is this the expected behaviour ?

Ciao
  Volker

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2009-01-19 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  0:08 Dr. Volker Zell
2009-01-15  5:25 ` Eric Blake
2009-01-19 15:51   ` Dr. Volker Zell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7zsknf2t7b.fsf@vzell-de.de.oracle.com \
    --to=dr.volker.zell@oracle.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).