From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Cc: emacs-devel@gnu.org
Subject: Re: Issues with Windows gcc -mno-cygwin (Mingw)
Date: 20 Mar 2003 00:36:08 +0100 [thread overview]
Message-ID: <m3n0jrylnb.fsf@cicero.benny.turtle-trading.net> (raw)
In-Reply-To: <m2n0jsy1hy.fsf@nyaumo.jasonr.f2s.com>
Hi Jason,
Jason Rumney <jasonr@gnu.org> writes:
> Ultimately cygwin should fix their port of make to pass paths that
> Windows programs expect,
I thought that the option --win32 that is supported by Cygwin helps,
but it doesn't. In addition the Emacs Makefiles don't work in that
mode, they somehow depend on --unix (the opposite option). If the
Emacs Makefiles would work in --win32 mode, that mode could probably
be changed to use a Windows style path for CURDIR, I would think that
using Cygwin paths in --win32 mode is a bug.
At the moment that option seems like more work than I would want to
handle.
> but if you would like to work on a conditional that does not break
> the build with mingw32 versions of make or when older versions of
> cygpath are installed, go ahead.
I'll see what I can do.
> I don't understand what problem this is fixing. Can you explain some
> more?
See my reply to Eli.
so long, benny
next prev parent reply other threads:[~2003-03-19 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 17:14 Issues with Windows gcc -mno-cygwin (Mingw) Benjamin Riefenstahl
2003-03-18 17:54 ` Eli Zaretskii
2003-03-19 23:31 ` Benjamin Riefenstahl
2003-03-20 4:30 ` Eli Zaretskii
2003-03-20 8:29 ` Jason Rumney
2003-03-20 16:21 ` Benjamin Riefenstahl
2003-03-18 18:26 ` Jason Rumney
2003-03-19 23:36 ` Benjamin Riefenstahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 7:39 David PONCE
2003-03-19 8:41 ` Jason Rumney
2003-03-19 23:44 ` Benjamin Riefenstahl
2003-03-19 23:40 ` Benjamin Riefenstahl
2003-03-19 9:29 David PONCE
2003-05-14 7:27 David PONCE
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=m3n0jrylnb.fsf@cicero.benny.turtle-trading.net \
--to=benjamin.riefenstahl@epost.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.