From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: 58832@debbugs.gnu.org, akrl@sdf.org
Subject: bug#58832: problems with native compilation
Date: Fri, 28 Oct 2022 13:28:47 +0200 [thread overview]
Message-ID: <5829EDD0-1195-40F4-B5AC-134B8B65591C@univie.ac.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Since I updated my operation system to macos 14, Ventura, issuing „—with-native-compilation" at the configure state is of no effect anymore for the resulting Emacs.app; the result is the same as it is without this option. Here is the error message coming out with the first option:
configure: error: The installed libgccjit failed to compile and run a test program using
the libgccjit library; see config.log for the details of the failure.
A look to config.log then shows:
configure:19456: gcc -E conftest.c
conftest.c:124:10: fatal error: 'libgccjit.h' file not found
#include <libgccjit.h>
Another look yields:
dylib (/opt/homebrew/Cellar/libgccjit/12.2.0/lib/gcc/current/libgccjit.dylib) was built for newer macOS version (13.0) than being linked (12.3)
Let me also remark that I have an M1 processor, and that I found nothing in the manuals dealing with such difficulties.
Konrad
[-- Attachment #2: Type: text/html, Size: 2827 bytes --]
next reply other threads:[~2022-10-28 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 11:28 Konrad Podczeck [this message]
2022-10-28 12:01 ` bug#58832: problems with native compilation Gerd Möllmann
2022-10-28 12:38 ` Konrad Podczeck
2022-10-28 12:54 ` Gerd Möllmann
2022-10-28 13:02 ` Konrad Podczeck
2022-10-28 15:32 ` Gerd Möllmann
2022-10-28 19:23 ` Konrad Podczeck
[not found] ` <DF205D70-486F-424A-94CC-9C061E53A345@univie.ac.at>
[not found] ` <m2bkpvuv9w.fsf@Mini.fritz.box>
[not found] ` <26824968-C3C1-43E2-A382-5096E31EA292@univie.ac.at>
[not found] ` <m24jvnhy1g.fsf@Mini.fritz.box>
2022-11-03 5:51 ` Gerd Möllmann
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=5829EDD0-1195-40F4-B5AC-134B8B65591C@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=58832@debbugs.gnu.org \
--cc=akrl@sdf.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.