From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-devel@gnu.org
Subject: Re: native compilation version on AArch64 running Debian 9.9
Date: Wed, 10 Mar 2021 15:35:34 +0000 [thread overview]
Message-ID: <877dmfxbqx.fsf@ucl.ac.uk> (raw)
In-Reply-To: 83wnufnlmv.fsf@gnu.org
On Wednesday, 10 Mar 2021 at 16:12, Eli Zaretskii wrote:
> Run the same compilation that the configure test does, but add -v to
> the GCC command-line options. Then look at the output, which should
> show which directories are searched for libraries during the link
> step.
Okay, this helps! I have found that Debian allowed me to install
(minor) version 8 of the libgccjit library although gcc expects version
6. Found version 6 (from Debian oldstable aka stretch) and installed it
and I get further. I am surprised that Debian's apt allowed me to
install the wrong version. Interesting!
I am still having difficulties with configure and native compilation but
I now know the root of all the problems (a very hacked/fragile Debian
installation). The problems I have now may lead me down a deep rabbit
hole (to do with mpfr library at the moment but I'm sure others will
crop up)... I will update if I ever come back out. :-)
Thank you all for your help.
--
Eric S Fraga via Emacs 28.0.50 & org 9.4.4 on Debian bullseye/sid
next prev parent reply other threads:[~2021-03-10 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 11:41 native compilation version on AArch64 running Debian 9.9 Eric S Fraga
2021-03-10 12:23 ` Eli Zaretskii
2021-03-10 12:31 ` Eric S Fraga
2021-03-10 12:49 ` Andreas Schwab
2021-03-10 13:16 ` Eric S Fraga
2021-03-10 13:48 ` Eli Zaretskii
2021-03-10 13:54 ` Eric S Fraga
2021-03-10 14:12 ` Eli Zaretskii
2021-03-10 15:35 ` Eric S Fraga [this message]
2021-03-11 8:49 ` Eric S Fraga
2021-03-11 19:26 ` Andrea Corallo via Emacs development discussions.
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=877dmfxbqx.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).