From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCHES] 21.3.50 for Cygwin: patch 3
Date: Wed, 25 Dec 2002 07:59:03 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1021225075032.7483A-100000@is> (raw)
In-Reply-To: <asqqhf$797$1@main.gmane.org>
Thank you for working on this.
I have some comments, below.
On Fri, 6 Dec 2002, Joe Buehler wrote:
> Some Cygwin commands (e.g. cp) work transparently with or without the .exe
> extension on an executable file, but some commands (e.g. ln, chmod,
> chgrp, chown) require the exact file name.
Is running a program via a Makefile rule one of those cases? I'd think
it isn't, in which case changes like this one:
> TAGS:
> - ../lib-src/etags $(srcdir)/*.[ch]
> + ../lib-src/etags@EXEEXT@ $(srcdir)/*.[ch]
are unnecessary.
Btw, perhaps you should suggest to the Cygwin maintainers a change in the
ported `install' (from GNU Fileutils/Coreutils) such that when invoked
with a command "install foo /bin/foo" it will look for foo.exe if foo is
not found. That will make `install:' targets in Makefiles work out of
the box.
> - rm -f emacs-* emacs
> + rm -f emacs-*@EXEEXT@ emacs@EXEEXT@
Why can't the "emacs-*" part be left alone here? It does match file
names that end in .exe, right?
> - -rm -f emacs emacs-* ../etc/DOC*
> + -rm -f emacs@EXEEXT@ emacs-*@EXEEXT@ ../etc/DOC*
Same here.
next prev parent reply other threads:[~2002-12-25 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 18:33 [PATCHES] 21.3.50 for Cygwin: patch 3 Joe Buehler
2002-12-25 5:59 ` Eli Zaretskii [this message]
2002-12-25 6:00 ` Eli Zaretskii
2003-01-03 16:21 ` Joe Buehler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.91.1021225075032.7483A-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).