Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Track down a failure involving shr
Date: Sun, 21 Dec 2014 06:51:50 -0500	[thread overview]
Message-ID: <877fxlxlt5.fsf@reader.local.lan> (raw)
In-Reply-To: <873889p4q8.fsf@cougar.home.aneadesign.com>

Clemens Schüller <cs.mlists+gnus@mailbox.org> writes:

> Cutout from my package.use
>
> app-editors/emacs-vcs xft gconf gfile gsettings gzip-el imagemagick libxml2 m17n-lib sound toolkit-scroll-bars
>
> It should install the libxml2 package automatically.

Thanks, I ended up with package.use like this:

=app-editors/emacs-vcs-25.0.9999-r1 Xaw3d athena libxml2 toolkit-scroll-bars imagemagick -acl -alsa -gtk -gtk3

And passed in 2 additional configure flags for good measure. Only the
first of which was probably needed:

EXTRA_ECONF="--with-x-toolkit=LUCID --with-toolkit-scroll-bars" \
  emerge -v app/editors-[...] 

[ebuild   R   *] app-editors/emacs-vcs-25.0.9999-r1:25

USE="X Xaw3d athena dbus gif gpm imagemagick inotify jpeg libxml2 png
svg tiff toolkit-scroll-bars xpm zlib -acl -alsa (-aqua) -games -gconf
-gfile -gnutls -gsettings -gtk -gtk3 -gzip-el -hesiod -kerberos
-livecd -m17n-lib -motif -pax_kernel (-selinux) -sound -source
-wide-int -xft"

Anyway, now emacs doesn't balk at opening gwene msgs.




  reply	other threads:[~2014-12-21 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20 21:16 Harry Putnam
2014-12-20 21:57 ` Adam Sjøgren
2014-12-20 22:45 ` Steinar Bang
2014-12-20 22:52   ` Clemens Schüller
2014-12-20 23:19     ` Harry Putnam
2014-12-21  6:35       ` Adam Sjøgren
2014-12-21 12:27       ` Clemens Schüller
2014-12-21 11:51         ` Harry Putnam [this message]
2014-12-20 22:54   ` Harry Putnam

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=877fxlxlt5.fsf@reader.local.lan \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).