unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: silverburgh.meryl@gmail.com, emacs-devel@gnu.org
Subject: Re: Compiling emacs 22 on ubuntu 7.0.4
Date: Wed, 13 Jun 2007 20:23:11 +0300	[thread overview]
Message-ID: <usl8vixa8.fsf@gnu.org> (raw)
In-Reply-To: <E1HyNsV-0006A4-Jf@fencepost.gnu.org> (message from Richard Stallman on Wed, 13 Jun 2007 04:06:55 -0400)

> From: Richard Stallman <rms@gnu.org>
> Date: Wed, 13 Jun 2007 04:06:55 -0400
> Cc: silverburgh.meryl@gmail.com, jan.h.d@swipnet.se, emacs-devel@gnu.org
> 
> The problem I am talking about is not just about icons.
> Emacs ought to support various graphics formats,
> if their libraries are installed.  If they are not installed,
> why should Emacs build without complaint and then lack the
> functionality?  I think it's a mistake.

I'm not sure I understand what scenario you were talking about.  The
origin of this thread was about a Windows build, where it is not
uncommon for the binaries to be built on one system, and then run on
many others (we provide precompiled Windows binaries on ftp.gnu.org).
In this scenario, while the machine where Emacs was built would
normally have all the image libraries (since Emacs developers
generally have them installed), we cannot assume anything about the
end-user machine.

In any case, the Windows configure script clearly says whether it did
or did not find each one of the image support libraries, although
those messages might not stand out enough among other configure-time
messages.

  parent reply	other threads:[~2007-06-13 17:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11  4:44 Compiling emacs 22 on ubuntu 7.0.4 Meryl Silverburgh
2007-06-11  5:20 ` Nick Roberts
2007-06-11  6:27   ` Jan Djärv
2007-06-11  6:49     ` Nick Roberts
2007-06-11 16:25       ` Richard Stallman
2007-06-11 17:48       ` Jan Djärv
     [not found]   ` <701fce30706102236y19574300r15ec9e5739e826f@mail.gmail.com>
2007-06-11  6:35     ` Nick Roberts
2007-06-11  6:01 ` Jan Djärv
2007-06-11 16:25   ` Richard Stallman
2007-06-11 17:57     ` Jan Djärv
2007-06-13  8:07       ` Richard Stallman
2007-06-11 21:39     ` Jason Rumney
2007-06-13  8:06       ` Richard Stallman
2007-06-13  9:18         ` Jan Djärv
2007-06-13  9:30           ` David Kastrup
2007-06-13 10:26             ` Jan Djärv
2007-06-13 10:40               ` David Kastrup
2007-06-13 20:45                 ` Jan Djärv
2007-06-13 22:35                   ` Glenn Morris
2007-06-14  6:14                     ` Jan Djärv
2007-06-14 20:14                       ` Glenn Morris
2007-06-14 16:20                     ` Richard Stallman
2007-06-14 20:18                       ` Glenn Morris
2007-06-14 20:44                         ` David Kastrup
2007-06-15  5:52                           ` Jan Djärv
2007-06-15 19:21                           ` Richard Stallman
2007-06-15 19:21                         ` Richard Stallman
2007-06-14 16:20                   ` Richard Stallman
2007-06-13  9:34           ` David House
2007-06-14  7:49           ` Richard Stallman
2007-06-14  8:23             ` Jan Djärv
2007-06-13 17:23         ` Eli Zaretskii [this message]
2007-06-13 17:41           ` Eli Zaretskii

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=usl8vixa8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=silverburgh.meryl@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).