From: Andreas Schwab <schwab@linux-m68k.org>
To: Alan Third <alan@idiocy.org>
Cc: bryan.m.obrien@gmail.com, 47558@debbugs.gnu.org,
Andrea Corallo <akrl@sdf.org>
Subject: bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos
Date: Wed, 07 Apr 2021 12:31:52 +0200 [thread overview]
Message-ID: <87blaqfkrr.fsf@igel.home> (raw)
In-Reply-To: <YG2CMRO4hKNaWKkp@breton.holly.idiocy.org> (Alan Third's message of "Wed, 7 Apr 2021 10:58:09 +0100")
On Apr 07 2021, Alan Third wrote:
> On Wed, Apr 07, 2021 at 09:08:36AM +0000, Andrea Corallo wrote:
>> A curiosity looking at c35a515a2f:
>>
>> + LDFLAGS="$LDFLAGS -L${BREW_LIBGCCJIT_PREFIX}/lib/gcc/10 -I${BREW_LIBGCCJIT_PREFIX}/include"
>> ^^^
>>
>> Does this mean will have to touch configure.ac when brew will provide gcc11?
>
> I think so. I can't see any way to get this path information out of
> the brew command. Perhaps we need to do some find magic to get the
> actual directory...?
gcc -print-file-name=libgccjit.so
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-04-07 10:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 1:36 bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos Bryan O'Brien
2021-04-02 5:46 ` Eli Zaretskii
2021-04-02 16:29 ` Alan Third
2021-04-02 18:39 ` Eli Zaretskii
2021-04-02 21:51 ` Alan Third
2021-04-03 6:32 ` Eli Zaretskii
2021-04-03 14:01 ` Alan Third
2021-04-03 14:17 ` Eli Zaretskii
2021-04-04 7:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 10:34 ` Alan Third
2021-04-05 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-05 21:14 ` Alan Third
2021-04-06 7:56 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 10:00 ` Alan Third
2021-04-06 14:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 17:36 ` Alan Third
2021-04-06 19:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 21:11 ` Alan Third
2021-04-06 21:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-06 21:33 ` Alan Third
2021-04-07 2:08 ` Bryan O'Brien
2021-04-07 7:53 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 8:18 ` Alan Third
2021-04-07 9:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 9:58 ` Alan Third
2021-04-07 10:31 ` Andreas Schwab [this message]
2021-04-07 10:35 ` Andreas Schwab
2021-04-07 10:48 ` Alan Third
2021-04-07 11:50 ` Eli Zaretskii
2021-04-07 12:15 ` Eli Zaretskii
2021-04-07 12:31 ` Alan Third
2021-04-07 11:45 ` Eli Zaretskii
2021-04-07 14:20 ` Alan Third
2021-04-07 14:25 ` Eli Zaretskii
2021-04-07 18:41 ` Bryan O'Brien
2021-04-07 18:45 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-07 16:46 ` Eli Zaretskii
2021-04-07 18:30 ` Bryan O'Brien
2021-04-07 18:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87blaqfkrr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=47558@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=alan@idiocy.org \
--cc=bryan.m.obrien@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).