From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, rms@gnu.org, Leo <sdl.web@gmail.com>
Subject: Re: Should libXt-devel be required to build Emacs?
Date: Fri, 22 Dec 2006 08:40:58 +0100 [thread overview]
Message-ID: <458B8C0A.5070801@swipnet.se> (raw)
In-Reply-To: <8764c5uv7s.fsf@stupidchicken.com>
Chong Yidong skrev:
> There's a problem with this: Autoconf 2.61 was only released in
> November this year, and it requires a new version of M4 (1.4.8), which
> in turn requires a new libc6. Most existing GNU/Linux distributions
> won't have these packages (at least in their "stable" branches).
What is it in m4 1.4.8 that needs a new libc upgrade? It sounds incredible.
Are you sure it isn't just some package system that has that requirement?
Most package systems seems to have problems with dependencies. For example on
Ubuntu Edgy, if I try to remove the X11 driver for my video card, the package
handler insists that the whole X11 be removed as well. Silly indeed.
Jan D.
next prev parent reply other threads:[~2006-12-22 7:40 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
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 [this message]
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
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=458B8C0A.5070801@swipnet.se \
--to=jan.h.d@swipnet.se \
--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 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).