From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Subject: Re: Compiling CVS Emacs with X toolkit
Date: Fri, 24 Nov 2006 01:02:28 +0200 [thread overview]
Message-ID: <87slg9kbqz.fsf@kobe.laptop> (raw)
In-Reply-To: 1164302540.601378.42030@m7g2000cwm.googlegroups.com
On 23 Nov 2006 09:22:20 -0800,
"Robert Thorpe" <rthorpe@realworldtech.com> wrote:
> Giorgos Keramidas wrote:
>> Right... and a few other X11-related libraries.
>>
>> % keramida@kobe:/home/keramida$ emacs --batch \
>> % --eval '(princ (format "%s\n" (version)))'
>> % GNU Emacs 22.0.91.2 (i386-unknown-freebsd7.0, X toolkit)
>> % of 2006-11-22 on kobe
>> % keramida@kobe:/home/keramida$ ldd /opt/emacs/bin/emacs
>> % /opt/emacs/bin/emacs:
>> [...]
>
> Wow. I haven't even heard of some of those libraries. It looks like
> image support is the reason for most of those libs being needed. Emacs
> has changed a lot since v20.7 when I looked at this last.
FWIW,
Yes, a lot of these are probably a result of the local configuration.
I usually build a local CVS snapshot of Emacs 22 with:
./configure --prefix='/opt/emacs' --with-x --with-x-toolkit=lucid \
--with-xpm --with-jpeg --with-tiff --with-gif --with-png
This includes *all* the graphics libraries which Emacs can work with in
X11, except for GTK+ widget support. I haven't been able to track down
a minor bug which causes Emacs to dump core on FreeBSD 7.0-CURRENT when
I enable GTK+ widget support, but the `lucid' toolkit works fine and has
been working for several months now (with the options shown above) :)
- Giorgos
next prev parent reply other threads:[~2006-11-23 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 14:46 Compiling CVS Emacs with X toolkit Mathias Dahl
2006-11-22 21:13 ` Sean Sieger
2006-11-22 21:33 ` Giorgos Keramidas
2006-11-23 14:59 ` Robert Thorpe
2006-11-23 16:55 ` Giorgos Keramidas
2006-11-23 17:22 ` Robert Thorpe
2006-11-23 23:02 ` Giorgos Keramidas [this message]
2006-11-24 17:51 ` Leo
2006-11-23 17:20 ` Mathias Dahl
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=87slg9kbqz.fsf@kobe.laptop \
--to=keramida@ceid.upatras.gr \
/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.