all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: emacs-26 build breaking on RHEL 6.6 GTK2
Date: Wed, 24 Jan 2018 13:26:52 -0500	[thread overview]
Message-ID: <bah8rbun83.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874lnbjfp0.fsf@gmail.com> (Robert Pluim's message of "Wed, 24 Jan 2018 19:04:59 +0100")

Robert Pluim wrote:

> [1]  Did we ever get anywhere on a CI setup for emacs?

"We" already have one. I find it irritating that it is ignored,
given the effort that has gone into it.

But yes, there is apparently a plan to make a new setup that will be
different, and perhaps it will (somehow) test all possible build
combinations.

I still think the onus is on people changing the display code to at
least check that it compiles with the common toolkit options,
particularly on the release branch at a time like this.



  reply	other threads:[~2018-01-24 18:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 15:48 emacs-26 build breaking on RHEL 6.6 GTK2 Kaushal Modi
2018-01-24 15:53 ` Kaushal Modi
2018-02-20 11:04   ` Robert Pluim
2018-02-20 15:22     ` Kaushal Modi
2018-02-20 16:21       ` Robert Pluim
2018-01-24 16:12 ` Robert Pluim
2018-01-24 17:28   ` Kaushal Modi
2018-01-24 17:46 ` Glenn Morris
2018-01-24 18:04   ` Robert Pluim
2018-01-24 18:26     ` Glenn Morris [this message]
2018-01-24 18:39       ` Robert Pluim
2018-01-24 18:43         ` Noam Postavsky
2018-01-24 18:32     ` martin rudalics
2018-01-24 18:41       ` Robert Pluim
2018-01-24 18:47         ` martin rudalics
2018-01-24 18:52           ` Robert Pluim
2018-01-24 19:16             ` martin rudalics
2018-01-24 19:22               ` Robert Pluim
2018-01-24 20:10             ` Eli Zaretskii
2018-01-24 20:19               ` martin rudalics

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=bah8rbun83.fsf@fencepost.gnu.org \
    --to=rgm@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 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.