From: Eli Zaretskii <eliz@gnu.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: native compilation version on AArch64 running Debian 9.9
Date: Wed, 10 Mar 2021 16:12:08 +0200 [thread overview]
Message-ID: <83wnufnlmv.fsf@gnu.org> (raw)
In-Reply-To: <87eegnxgex.fsf@ucl.ac.uk> (message from Eric S Fraga on Wed, 10 Mar 2021 13:54:46 +0000)
> From: Eric S Fraga <e.fraga@ucl.ac.uk>
> Date: Wed, 10 Mar 2021 13:54:46 +0000
>
> On Wednesday, 10 Mar 2021 at 15:48, Eli Gretzky wrote:
> > If it just repeats the argument, it means GCC cannot find the library,
> > probably because it looks in the wrong places.
>
> Indeed. And that's what I cannot understand and need some pointers to
> see if I can fix the problem.
>
> Emacs builds just fine without the native compilation option so
> obviously gcc compiles and runs the various tests in the configure
> file. Only the jit aspect fails in finding the library.
>
> I have looked at /etc/ld.so.conf (and .d), for instance, and everything
> looks fine. Does anybody have any suggestion as to where &/or how gcc
> might be getting misinformed?
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.
next prev parent reply other threads:[~2021-03-10 14:12 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 [this message]
2021-03-10 15:35 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wnufnlmv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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 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.