unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: stephen.berman@gmx.net, dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure	on Windows]
Date: Wed, 04 Jun 2014 00:02:08 +0300	[thread overview]
Message-ID: <83r435906n.fsf@gnu.org> (raw)
In-Reply-To: <538E29C3.401@cs.ucla.edu>

> Date: Tue, 03 Jun 2014 13:02:11 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> 
> On 06/03/2014 11:51 AM, Stephen Berman wrote:
> > I'll wait till the dust settles, in case
> > the requirement is reverted for Gtk+ builds.
> 
> I tried to fix this in trunk bzr 117250, so that you shouldn't need 
> libXt-devel installed any more.  The new approach was having problems in 
> --with-ns builds too.  This latest change affects the Windows builds; I 
> hope I caught all the problems there, though I can't easily test Windows.

You did allright for Windows, but then broke it all by the sysselect.h
changes.  I fixed that in r117252.



  reply	other threads:[~2014-06-03 21:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 15:11 build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure on Windows] Stephen Berman
2014-06-03 16:04 ` Eli Zaretskii
2014-06-03 16:13   ` Eli Zaretskii
2014-06-03 16:41     ` Stephen Berman
2014-06-03 17:02       ` Eli Zaretskii
2014-06-03 17:13         ` Eli Zaretskii
2014-06-03 17:24           ` Dmitry Antipov
2014-06-03 17:29         ` Dmitry Antipov
2014-06-03 17:52           ` Glenn Morris
2014-06-03 18:16             ` Dmitry Antipov
2014-06-03 18:51           ` Stephen Berman
2014-06-03 20:02             ` Paul Eggert
2014-06-03 21:02               ` Eli Zaretskii [this message]
2014-06-03 21:12               ` Stephen Berman

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=83r435906n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).