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: Thu, 06 Aug 2020 19:40:36 +0200	[thread overview]
Message-ID: <m2r1sj65bf.fsf@gmail.com> (raw)
In-Reply-To: <87y2mrn4jn.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 06 Aug 2020 17:05:16 +0100")

>>>>> On Thu, 06 Aug 2020 17:05:16 +0100, Eric S Fraga <e.fraga@ucl.ac.uk> said:

    Eric> Hello,
    Eric> Without giving all the gory details, I am trying to build a recent emacs
    Eric> 28.x version (from git) on an old computer running Debian Jessie,
    Eric> i.e. Linux circa 2014-2015.

    Eric> I can configure and compile Emacs if I use --with-gnutls=ifavailable but
    Eric> not having libgnutls-dev or libgmp-dev installed.  This Emacs then runs
    Eric> but has problems with accessing email (gnus).  I can live with this to
    Eric> some degree as it meets one of my main requirements which is for writing
    Eric> prose.  But it would be nice to have email on it as well.

Nothing stops you from using  lisp/obsolete/{tls,starttls}.el , which
will wrap gnutls-cli or 'openssl s_client' for you, although itʼs not
a path I'drecommend.

    Eric> If I install the gnutls library, this brings in libgmp and then Emacs
    Eric> does not build.  I get error messages along the lines of:

    Eric> ,----
    Eric> | floatfns.o: In function `Fabs':
    Eric> | /home/ucecesf/git/emacs/src/floatfns.c:279: undefined reference to `mpz_sgn'
    Eric> | /home/ucecesf/git/emacs/src/floatfns.c:281: undefined reference to `mpz_neg'
    Eric> `----

    Eric> The strange thing is that mpz_sgn, for instance, is a #define in gpm.h
    Eric> but is not in gmpxx.h.  Both of these include files come from
    Eric> libgmp-dev.  It could be that Emacs's configure script picks up the
    Eric> wrong one?

    Eric> The versions of the two packages in question are:

    Eric> libgmp-dev:armhf        2:6.0.0+dfsg-6
    Eric> libgnutls28-dev:armhf   3.3.8-6+deb8u7   

    Eric> Am I doing something incredibly stupid (I have RTFMed but haven't seen
    Eric> anything that would help)?  Do I need to build those packages from
    Eric> source maybe?   

I think you can configure emacs using '--without-libgmp', then it will
use a builtin version of gmp. Iʼm assuming that linking to libgnutls
only has a runtime dependency on libgmp, not a requirement to have
access to gmp headers.

Maybe just uninstalling libgmp-dev but leaving libgmp installed is
enough?

Robert



  reply	other threads:[~2020-08-06 17:40 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 [this message]
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
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=m2r1sj65bf.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).