[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failure building with libgccjit under MacOS Monterey

From: Perry E. Metzger
Subject: Re: Failure building with libgccjit under MacOS Monterey
Date: Sat, 13 Nov 2021 18:58:05 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:95.0) Gecko/20100101 Thunderbird/95.0

On 11/13/21 02:21, Eli Zaretskii wrote:
Date: Fri, 12 Nov 2021 21:23:58 +0000
From: Alan Third <alan@idiocy.org>
Cc: emacs-devel <emacs-devel@gnu.org>

Hmm, I don't see anything wrong with the command lines. It looks like
the error is actually being caused by the attempt to set up or use
libgccjit within the smoketest.

I don't know anything about how that works. The full error text for
anyone interested is below.

configure:17126: /usr/bin/cc -o conftest -g3 -O2 -I/opt/local/include/librsvg-2.0 
-I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include -I/opt/local/include/cairo 
-I/opt/local/include -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include 
-I/opt/local/include -I/opt/local/include/pixman-1 -I/opt/local/include 
-I/opt/local/include/ossp -I/opt/local/include/freetype2 -I/opt/local/include 
-I/opt/local/include/libpng16 -I/opt/local/include -I/opt/local/include/gcc11   
-I/opt/local/include -I/opt/local/include/gcc11 -L/opt/local/lib 
-L/opt/local/lib/gcc11 conftest.c -lgccjit   -L/opt/local/lib/gcc11 >&5
configure:17126: $? = 0
configure:17126: ./conftest
ld: library not found for -lSystem  <<<<<<<<<<<<<<<<<<<<<<<
collect2: error: ld returned 1 exit status
libgccjit.so: error: error invoking gcc driver
configure:17126: $? = 1
configure: program exited with status 1
The line I highlighted seems to say that some dependency library is
missing, and the linker therefore fails to link the text program.

What's weird here is that more or less nothing happened; it simply broke in the last few weeks. I'm guessing, though, that I'm the only person in a position to figure this out so I'll start digging. (I was kind of hoping it was a known issue and someone else had seen it previously.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]