GNU bug report logs - #48804
27.2; compilation emacs on macOS

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Niels Søndergaard <nisoni <at> algon.dk>
Cc: alan <at> idiocy.org, nisoni <at> algon.dk, konrad.podczeck <at> univie.ac.at, 48804 <at> debbugs.gnu.org
Subject: bug#48804: 27.2; compilation emacs on macOS
Date: Fri, 04 Jun 2021 21:55:50 +0300

> From: Niels Søndergaard <nisoni <at> algon.dk>
> Date: Fri, 4 Jun 2021 17:15:30 +0200
> Cc: Alan Third <alan <at> idiocy.org>,
>  Eli Zaretskii <eliz <at> gnu.org>,
>  konrad.podczeck <at> univie.ac.at,
>  48804 <at> debbugs.gnu.org
> 
> with: ./configure --without-ns --with-x-toolkit=no -with-native-compilation --with-mailutils
> which is not what I really wants,
> 
> we’re back to the original failure:
> 
> checking libgccjit.h usability... yes
> checking libgccjit.h presence... yes
> checking for libgccjit.h... 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.
> The test program can be found here:
> <https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>.
> You can try compiling it yourself to investigate the issues.
> Please report the issue to your distribution if libgccjit was installed
> through that.

Don't set CC in the environment.  Instead, add the directory where the
gcc compiler driver (the 'gcc' executable file) is installed to your
PATH, but after the directory where clang is installed.  Also, make
sure you don't have on PATH a 'gcc' executable that actually calls
clang.

The problem is that you need clang as your compiler to build Emacs,
but you need to arrange for libgccjit to find 'gcc' and its C compiler
('cc1').

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.