From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Track down a failure involving shr
Date: Sat, 20 Dec 2014 17:54:18 -0500 [thread overview]
Message-ID: <877fxmexut.fsf@reader.local.lan> (raw)
In-Reply-To: <86tx0qkkjf.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
>>>>>> Harry Putnam <reader@newsguy.com>:
>
>> Setup: Gentoo linux (new install)
>> emacs-25
>> gentoo pkg emacs-vcs which installs from the bzr trunk
>
> I thought emacs had moved from bzr to git?
I'm not really sure where emerge gets the source... I just `thought' it
would be bzr.
And the pkg was built using these use flags+
+ flags (those that are turned on):
X Xaw3d athena gif gpm gtk gtk3 imagemagick inotify jpeg png svg tiff
xpm zlib
- Flags (those that are turned off):
-acl -alsa (-aqua) -dbus -games -gconf -gfile -gnutls -gsettings
---gzip-el -hesiod -kerberos -libxml2 -livecd -m17n-lib -motif
-pax_kernel (-selinux) -sound -source -toolkit-scroll-bars -wide-int
--xft
So, infact emerge told the process NOT to build against libxml2
This is the exact version I installed:
app-editors/emacs-vcs-25.0.50_pre20141130:25
The ebuild shows the sources URI as: git://git.sv.gnu.org/emacs.git
So, I should have checked I guess, but I `thought' bzr was the repo
used.
prev parent reply other threads:[~2014-12-20 22:54 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
2014-12-20 22:54 ` Harry Putnam [this message]
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=877fxmexut.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).