unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: 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:10:28 +0100	[thread overview]
Message-ID: <87h7tamw17.fsf@ucl.ac.uk> (raw)
In-Reply-To: m2d03yk63m.fsf@gmail.com

On Monday, 10 Aug 2020 at 15:01, Robert Pluim wrote:
> Glad it worked. Which millenium was this sytem from again? ;-)

Software 6 years old and hardware 10 years old which in computing means
16th century? ;-)

But, more seriously, it's depressing that I keep going back to some of
my old systems in preference to "newer supposedly more advanced"
systems.  In this case, it's a wee OpenPandora palmtop which still works
better than an 8 year later iteration from another company.

The same applies to one of my phones: my Nokia N900 (2008 vintage) still
runs metaphoric rings around any Android phone including my S20+, brand
new this year. But I haven't tried getting Emacs running on the
N900... :-)

> 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.

Understood.  Sounds reasonable.  At least I know what I have to do now.

Thanks again for all your help (and your patience!),
eric

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid




  reply	other threads:[~2020-08-10 14:10 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
2020-08-10 14:10           ` Eric S Fraga [this message]
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=87h7tamw17.fsf@ucl.ac.uk \
    --to=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).