From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Kevin Morio <kevin@morio.me>, 56738-done@debbugs.gnu.org
Subject: bug#56738: Cannot find libgccjit.dylib on macOS
Date: Thu, 4 Aug 2022 14:14:07 +0000 [thread overview]
Message-ID: <CADwFkmnq_LDf9wZ8R1B4x6j6bsGiKS6o2PGHjGM9++ACdaN4vw@mail.gmail.com> (raw)
In-Reply-To: <83tu76fzc7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 24 Jul 2022 15:51:36 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Kevin Morio <kevin@morio.me>
>> Date: Sun, 24 Jul 2022 12:15:17 +0200
>>
>> Dear Emacs maintainers,
>>
>> Emacs 28.1.90 (282dde887db163b25b31fba3bf10a80f2b93203c) fails to build on
>> macOS 12.4 when configured with the following invocation:
>>
>> ./configure —with-native-compilation
>> ...
>> usage: dirname string [...]
>> checking for gcc_jit_context_acquire in -lgccjit... no
>> configure: error: ELisp native compiler was requested, but libgccjit was not found.
>> Please try installing libgccjit or a similar package.
>> If you are sure you want Emacs be compiled without ELisp native compiler,
>> pass the --without-native-compilation option to configure.
>>
>> This is the same bug as bug#55173 which has been reported for
>> Emacs 29.0.50 (a41a181db5f3aca043ed42b228dc56a6403c21a5)
>> and fixed in commit
>> faa29fa2c9e9d5a5d7544a1a39b2a89cf57a8439
>> with the following patch
>
> Thanks, I've now cherry-picked that change to the emacs-28 branch, and
> it will be part of the upcoming Emacs 28.2.
No further comments within a week, so I'm closing this bug report.
prev parent reply other threads:[~2022-08-04 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 10:15 bug#56738: Cannot find libgccjit.dylib on macOS Kevin Morio
2022-07-24 12:51 ` Eli Zaretskii
2022-08-04 14:14 ` Stefan Kangas [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
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=CADwFkmnq_LDf9wZ8R1B4x6j6bsGiKS6o2PGHjGM9++ACdaN4vw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=56738-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin@morio.me \
/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).