all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Should libXt-devel be required to build Emacs?
Date: Wed, 20 Dec 2006 23:57:42 -0500	[thread overview]
Message-ID: <E1GxFzy-0008I5-Ar@fencepost.gnu.org> (raw)
In-Reply-To: <m2hcvq33gk.fsf@sl392.st-edmunds.cam.ac.uk> (message from Leo on Wed, 20 Dec 2006 17:02:51 +0000)

    I report this using autoconf 2.59. So this bug will exist in the
    pretest.

It appears that we need to switch to using Autoconf 2.61, for the
pretests and releases.

And this line in configure.in

    AC_PREREQ(2.54)dnl

should be updated to say 2.61.

  reply	other threads:[~2006-12-21  4:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 17:25 Should libXt-devel be required to build Emacs? Leo
2006-12-19  6:55 ` Jan Djärv
2006-12-19 13:12   ` Leo
2006-12-19 20:36     ` Jan Djärv
2006-12-19 20:52       ` Leo
2006-12-20 16:00         ` Jan Djärv
2006-12-20 16:41           ` Chong Yidong
2006-12-20 17:02             ` Leo
2006-12-21  4:57               ` Richard Stallman [this message]
2006-12-21 15:25                 ` Chong Yidong
2006-12-21 23:18                   ` Richard Stallman
2006-12-21 23:57                     ` Chong Yidong
2006-12-22  7:43                       ` Jan Djärv
2006-12-22 11:17                         ` Eli Zaretskii
2006-12-23 20:13                       ` Richard Stallman
2006-12-23 20:43                         ` Henrik Enberg
2006-12-23 22:12                           ` Jan Djärv
2006-12-23 22:25                             ` Henrik Enberg
2006-12-24 10:06                               ` Jan Djärv
2006-12-24 17:09                           ` Richard Stallman
2006-12-22 19:25                     ` Chong Yidong
2006-12-23 20:14                       ` Richard Stallman
2006-12-22  7:40                   ` Jan Djärv
2006-12-20 17:14             ` Jan Djärv

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=E1GxFzy-0008I5-Ar@fencepost.gnu.org \
    --to=rms@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.