unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: problems building emacs with libgpm & gnutls on an old Debian system (Jessie)
Date: Mon, 10 Aug 2020 15:01:17 +0200	[thread overview]
Message-ID: <m2d03yk63m.fsf@gmail.com> (raw)
In-Reply-To: <87bljioil6.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 10 Aug 2020 12:17:57 +0100")

>>>>> On Mon, 10 Aug 2020 12:17:57 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:

    Eric> On Friday,  7 Aug 2020 at 12:49, Robert Pluim wrote:
    >> Or the system one is failing, in which case you can try the gnulib one
    >> by unsetting HAVE_GETRANDOM in src/config.h

    Eric> This worked!  Thank you.  I am not sure why the system one is failing
    Eric> but it does seem to be the case.  In any case, I now have a working
    Eric> Emacs built from src with gnus, org, twittering, etc.

Glad it worked. Which millenium was this sytem from again? ;-)

    Eric> It would be nice to have the option to control the use of getrandom from
    Eric> the configure script to avoid having to change the generated config
    Eric> files afterwards.

Emacs uses gnulib for this kind of stuff, and since itʼs all low-level
system calls, there are no configure level switches for turning it
off. Itʼs not like itʼs TLS support or an image library, which are optional.

Robert



  reply	other threads:[~2020-08-10 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 16:05 problems building emacs with libgpm & gnutls on an old Debian system (Jessie) Eric S Fraga
2020-08-06 17:40 ` Robert Pluim
2020-08-07 10:18   ` Eric S Fraga
2020-08-07 10:49     ` Robert Pluim
2020-08-10 11:17       ` Eric S Fraga
2020-08-10 13:01         ` Robert Pluim [this message]
2020-08-10 14:10           ` Eric S Fraga
2020-08-10 14:21             ` Robert Pluim

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2d03yk63m.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).