all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: cschol2112@googlemail.com, emacs-devel@gnu.org
Subject: Re: Compiling Emacs 23.1.92 on Windows fails
Date: Tue, 23 Feb 2010 20:27:18 +0200	[thread overview]
Message-ID: <83k4u3n6yh.fsf@gnu.org> (raw)
In-Reply-To: <jwvsk8ram4j.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Christoph <cschol2112@googlemail.com>
> Date: Tue, 23 Feb 2010 12:38:35 -0500
> 
> > Yes, that turned out to be the problem.
> > Using mingw32-make instead of cygwin's make worked and built successfully.
> 
> Thanks.  Eli, would it be possible to detect the use of cygwin's make
> and output a warning in that case?

If someone tells what does the Cygwin Make print under --version, and
if there's something Cygwin-specific there, then yes, we could test
that in nt/configure.bat.

Failing that, w32proc.c:w32_executable_type has code to detect Cygwin
executables by scanning their DLL import table for cygwin.dll.  We
could start the build by compiling a simple program to diagnose
make.exe using that method.  Seems a bit gross, though.




  reply	other threads:[~2010-02-23 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-20 22:46 Compiling Emacs 23.1.92 on Windows fails Christoph
2010-02-21  4:17 ` Eli Zaretskii
     [not found]   ` <4B80B4B3.3070609@gmail.com>
2010-02-23 17:38     ` Stefan Monnier
2010-02-23 18:27       ` Eli Zaretskii [this message]
2010-02-23 19:36         ` Óscar Fuentes
2010-02-24 14:56         ` Sean Sieger
2010-02-24 15:16           ` Sean Sieger
2010-02-24 18:37             ` Eli Zaretskii
2010-02-25  2:15               ` Sean Sieger
2010-02-25  2:55             ` Christoph

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=83k4u3n6yh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cschol2112@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.