From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: using gnus on windows
Date: Tue, 04 Sep 2012 20:24:03 +0300 [thread overview]
Message-ID: <83hardem6k.fsf@gnu.org> (raw)
In-Reply-To: <87hard20h1.fsf@gmail.com>
> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
> Date: Tue, 04 Sep 2012 18:53:46 +0200
> Cc: emacs-devel@gnu.org
>
> > I don't think using gnutls-cli under Windows is supported at all? The
> > recommended thing is to use an Emacs with libgnutls support compiled in,
> > and with the libgnutls libraries installed.
> This is not documented
Yes, it is, see README.W32.
> we even don't know if the windows binaries are compiled with this
> feature
??? Christoph always says that explicitly in his announcements. For
example:
> The Emacs Trunk Windows Binaries (bzr revno 109861) have been published in
>
> http://alpha.gnu.org/gnu/emacs/windows/
>
> The binaries were built using the following libraries:
> giflib-4.1.4-1
> gnutls-3.0.9 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> jpeg-6b-4
> libXpm-3.5.8
> libpng-1.4.3-1
> tiff-3.8.2-1
> zlib-1.2.5-2
> libxml2-2.7.8
> libiconv-1.13.1-1
Also, you should be able to see some hints in the value of
system-configuration-options.
> so it is hard to use Gnus on windows without spending hours of
> googling and reading code to figure out what to do.
README.W32 should spell all this out, please tell where it should be
improved if it doesn't.
However, if you need full control of what's in your build, you need to
build Emacs yourself. On any platform.
next prev parent reply other threads:[~2012-09-04 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 8:13 using gnus on windows Thierry Volpiatto
2012-09-04 15:32 ` Lars Ingebrigtsen
2012-09-04 16:53 ` Thierry Volpiatto
2012-09-04 17:24 ` Eli Zaretskii [this message]
2012-09-04 23:43 ` Christoph Scholtes
2012-09-05 4:41 ` Thierry Volpiatto
2012-09-05 14:35 ` Stefan Monnier
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=83hardem6k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=thierry.volpiatto@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 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.