all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Chong Yidong <cyd@stupidchicken.com>,
	emacs-devel@gnu.org, Richard Stallman <rms@gnu.org>,
	sdl.web@gmail.com
Subject: Re: Should libXt-devel be required to build Emacs?
Date: Sat, 23 Dec 2006 23:12:21 +0100	[thread overview]
Message-ID: <458DA9C5.9090101@swipnet.se> (raw)
In-Reply-To: <20061223204322.GA5902@printf.se>

Henrik Enberg skrev:
> Richard Stallman <rms@gnu.org> writes:
>>     > That's not so bad.  Most users don't need to rebuild the configure
>>     > file, so they won't have a problem.
>>     >
>>     > However, we could ask the Autoconf developers to release a patched
>>     > version 2.59.1 which fixes this bug and doesn't require a new M4.
>>
>>     On the other hand, most users don't compile Emacs at all; they use
>>     pre-packaged binaries; those that do compile Emacs can surely install
>>     libXt-dev.
>>
>> I don't remember all the details of the problem.  If libXt-dev is not
>> installed, what happens when configure is correctly built with
>> autoconf 2.61?  Does compilation fail because libXt-dev includes
>> things needed for compilation?  Or does compilation work?
> 
> I just built Emacs on a brand new Debian system, and without libXt-dev,
> the configure script doesn't find X11 at all, even when passing
> --with-x.  So you end up with a non-x enabled Emacs.
> 

But you probably didn't use autoconf 2.61.  If you had, you would have an X
enabled Emacs.

< 2.61 and no libXt-dev:  configure fails to find X at all.
2.61   and no libXt-dev:  configure finds X correctly.

Compilation works in both cases.

	Jan D.

  reply	other threads:[~2006-12-23 22:12 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
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 [this message]
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=458DA9C5.9090101@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=sdl.web@gmail.com \
    /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.