From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Dependencies for native compiling emacs not found
Date: Thu, 23 Dec 2021 22:19:10 +0200 [thread overview]
Message-ID: <83fsqjt6pt.fsf@gnu.org> (raw)
In-Reply-To: <877dbvozb8.fsf@posteo.net> (message from Thierry Volpiatto on Thu, 23 Dec 2021 20:08:50 +0000)
> From: Thierry Volpiatto <thievol@posteo.net>
> Cc: emacs-devel@gnu.org
> Date: Thu, 23 Dec 2021 20:08:50 +0000
>
> > I believe the actual problem in your case was that GCC 9 couldn't find
> > libgccjit from GCC 10, because it was looking in the wrong
> > subdirectory of /usr/lib/x86_64-linux-gnu/, since (AFAIU) libgccjit is
> > installed into a versioned subdirectory of that directory, and GCC
> > looks for it in the subdirectory that matches its version.
>
> Ah ok thanks for clarification, but I think for the end user like me it
> is better keeping up with same version of gcc/libgccjit to avoid
> complications to specify paths.
Yes, of course. I just wanted to set the record straight.
prev parent reply other threads:[~2021-12-23 20:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 9:30 Dependencies for native compiling emacs not found Thierry Volpiatto
2021-12-23 9:57 ` Eli Zaretskii
2021-12-23 12:56 ` Thierry Volpiatto
2021-12-23 13:17 ` Óscar Fuentes
2021-12-23 14:24 ` Eli Zaretskii
2021-12-23 15:51 ` Thierry Volpiatto
2021-12-23 16:15 ` Óscar Fuentes
2021-12-23 17:29 ` Thierry Volpiatto
2021-12-23 20:17 ` Óscar Fuentes
2021-12-23 20:49 ` Thierry Volpiatto
2021-12-23 16:20 ` Eli Zaretskii
2021-12-23 17:37 ` Thierry Volpiatto
2021-12-23 17:58 ` Manuel Uberti
2021-12-23 18:16 ` Andreas Schwab
2021-12-23 18:26 ` Thierry Volpiatto
2021-12-23 18:20 ` Eli Zaretskii
2021-12-23 18:27 ` Thierry Volpiatto
2021-12-23 19:16 ` Eli Zaretskii
2021-12-23 19:36 ` Thierry Volpiatto
2021-12-23 19:43 ` Eli Zaretskii
2021-12-23 20:08 ` Thierry Volpiatto
2021-12-23 20:19 ` Eli Zaretskii [this message]
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=83fsqjt6pt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=thievol@posteo.net \
/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.