From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs was compiled without networking support
Date: Fri, 13 Dec 2013 17:27:40 +0200 [thread overview]
Message-ID: <834n6c6aab.fsf@gnu.org> (raw)
In-Reply-To: <46A2D5D8-1A19-40C5-9987-62730B681939@web.de>
> From: Peter Dyballa <Peter_Dyballa@web.de>
> Date: Fri, 13 Dec 2013 15:33:35 +0100
> Cc: help-gnu-emacs@gnu.org
>
>
> Am 13.12.2013 um 15:28 schrieb Johan Andersson:
>
> > Why would that do any difference? I mean it works outside of the step in
> > the same process.
>
> To me it's not clear whether GNU Emacs itself performs networking or some tool in a sub-process provides network access for some Lisp code. When you can see that GNU Emacs uses TLS, than it's clear that some Lisp code is presumingly not working correctly. Then you could try to test behaviour with 'emacs -Q' or with a very minimal init file to just configure networking.
I don't see how this could be related to the OP's problem.
The error message seems to come from this place in network-stream.el:
(unless (featurep 'make-network-process)
(error "Emacs was compiled without networking support"))
As you see, it only tests a single feature, and that feature comes
from process.c, not from GnuTLS.
next prev parent reply other threads:[~2013-12-13 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 13:54 Emacs was compiled without networking support Johan Andersson
2013-12-13 14:20 ` Eli Zaretskii
2013-12-13 14:22 ` Peter Dyballa
2013-12-13 14:28 ` Johan Andersson
2013-12-13 14:33 ` Peter Dyballa
2013-12-13 14:35 ` Johan Andersson
2013-12-13 14:50 ` Peter Dyballa
2013-12-13 14:52 ` Johan Andersson
2013-12-13 15:04 ` Peter Dyballa
2013-12-13 15:07 ` Johan Andersson
2013-12-13 15:36 ` Peter Dyballa
2013-12-13 15:53 ` Johan Andersson
2013-12-13 15:27 ` Eli Zaretskii [this message]
2013-12-13 14:28 ` Peter Dyballa
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=834n6c6aab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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.