From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 57380@debbugs.gnu.org
Subject: bug#57380: 29.0.50; configure --config-cache --with-native-compilation failing
Date: Wed, 24 Aug 2022 15:31:20 +0300 [thread overview]
Message-ID: <83pmgp6cx3.fsf@gnu.org> (raw)
In-Reply-To: <m235dlhmho.fsf@Mini.fritz.box> (message from Gerd Möllmann on Wed, 24 Aug 2022 14:09:07 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Date: Wed, 24 Aug 2022 14:09:07 +0200
>
> The second configure, in the first recipe this is './config.status
> --recheck', fails with
>
> checking for gcc_jit_context_acquire in -lgccjit... (cached) yes
> checking for libgccjit.h... (cached) yes
> 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.
>
> Config.log says
>
> configure:19611: checking for libgccjit.h
> configure:19611: result: yes
> configure:19674: gcc -o conftest -g -O2 conftest.m -lgccjit -lsqlite3 -L/opt/homebrew/Cellar/libgccjit/12.1.0/lib/gcc/current >&5
> conftest.m:131:12: fatal error: 'libgccjit.h' file not found
> #include <libgccjit.h>
> ^~~~~~~~~~~~~
> 1 error generated.
Does the command to compile the test program look different in a
config.log from a successful build? If so, what is the difference?
(Perhaps some -I switch is missing?) And if there's no difference,
how come the same command sometimes succeeds and sometimes fails?
next prev parent reply other threads:[~2022-08-24 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 12:09 bug#57380: 29.0.50; configure --config-cache --with-native-compilation failing Gerd Möllmann
2022-08-24 12:31 ` Eli Zaretskii [this message]
2022-08-24 12:55 ` Gerd Möllmann
2022-08-24 13:30 ` Gerd Möllmann
2022-08-24 13:37 ` Gerd Möllmann
2022-08-24 14:23 ` Eli Zaretskii
2022-08-24 14:32 ` Andreas Schwab
2022-08-24 16:20 ` Gerd Möllmann
2022-08-25 9:16 ` 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
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=83pmgp6cx3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57380@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).