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 17:23:01 +0300 [thread overview]
Message-ID: <83czcp67qy.fsf@gnu.org> (raw)
In-Reply-To: <m2wnaxg3ub.fsf@Mini.fritz.box> (message from Gerd Möllmann on Wed, 24 Aug 2022 15:37:16 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 57380@debbugs.gnu.org
> Date: Wed, 24 Aug 2022 15:37:16 +0200
>
> Gerd Möllmann <gerd.moellmann@gmail.com> writes:
>
> >
> > Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> >
> >> AC_RUN_IFELSE is apparently run differently when using the cache, or
> >> something like that.
> >
> > Success and failure
> >
> > configure:19674: gcc -o conftest -g3 -O2 ... conftest.c
> > configure:19674: gcc -o conftest -g -O2 ... conftest.m
> > ^^
> >
> > Baffled.
>
> diff --git a/configure.ac b/configure.ac
> index 7616e450d0..08a41a7808 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -4273,6 +4273,7 @@ AC_DEFUN
> [], [libgccjit_not_found])
> AC_CHECK_HEADERS([libgccjit.h], [], [libgccjit_dev_not_found])
> # Check if libgccjit really works.
> + AC_LANG(C)
> AC_RUN_IFELSE([libgccjit_smoke_test], [], [libgccjit_broken])
> HAVE_NATIVE_COMP=yes
> case "${opsys}" in
>
> This makes it work for me.
Doh! Do you understand why it is only needed in one of the two cases?
And doesn't it affect the following tests?
> It that something for emacs-28, or rather not? Guess not, but just in
> case.
What does this call produce in the configure script?
next prev parent reply other threads:[~2022-08-24 14:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czcp67qy.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 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.