unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: CVS Emacs cygwin build problem.
Date: Sat, 20 May 2006 09:21:57 +0100	[thread overview]
Message-ID: <uwtchkswq.fsf@jasonrumney.net> (raw)
In-Reply-To: <93CB32FD-EC9D-47C9-B4B6-D7F28FB4A088@qwest.net> (Steven Wu's message of "Sat, 20 May 2006 01:09:44 -0700")

"Steven Wu" <wus@qwest.net> writes:

> ifdef CYGWIN
> lisp = $(shell cygpath -m $(CURDIR))
> else
> lisp = $(CURDIR)
> endif
>
> See this is need only in the makefile.w32-in. For those who compile
> window native Emacs using cygwin utils, this change can only help
> them, and it won't affect minGW. For those compile Emacs under
> cygwin, they don't use makefile.w32-in. I don't see what other system
> will be affected except maybe nmake.

Our previous experience is that it does affect mingw make, when run
under Cygwin bash.

  reply	other threads:[~2006-05-20  8:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  6:47 CVS Emacs cygwin build problem Steven Wu
2006-05-19  8:17 ` Jason Rumney
2006-05-19 14:08   ` Steven Wu
2006-05-19 11:33 ` Eli Zaretskii
2006-05-19 14:06   ` Steven Wu
2006-05-19 15:28     ` Eli Zaretskii
2006-05-20  3:48       ` Steven Wu
2006-05-20  7:45         ` Jason Rumney
2006-05-20  8:09           ` Steven Wu
2006-05-20  8:21             ` Jason Rumney [this message]
2006-05-20  9:03         ` Eli Zaretskii
2006-05-20 13:36           ` Steven Wu
2006-05-20 16:53             ` Eli Zaretskii
2006-05-21  0:56               ` Richard Stallman
2006-05-21  2:21                 ` Steven Wu
2006-05-21  3:34                 ` Eli Zaretskii
2006-05-22  2:38                   ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19  8:28 djh
2006-05-19 14:20 Steven Wu

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=uwtchkswq.fsf@jasonrumney.net \
    --to=jasonr@gnu.org \
    --cc=eliz@gnu.org \
    --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).