From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: bryan.m.obrien@gmail.com, akrl@sdf.org, schwab@linux-m68k.org,
47558@debbugs.gnu.org
Subject: bug#47558: 28.0.50; dlopen 'image not found' gccemacs native-lisp macos
Date: Wed, 07 Apr 2021 14:50:03 +0300 [thread overview]
Message-ID: <83zgya9uvo.fsf@gnu.org> (raw)
In-Reply-To: <YG2N993SkqQ2wvaU@breton.holly.idiocy.org> (message from Alan Third on Wed, 7 Apr 2021 11:48:23 +0100)
> Date: Wed, 7 Apr 2021 11:48:23 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: Andrea Corallo <akrl@sdf.org>, Eli Zaretskii <eliz@gnu.org>,
> bryan.m.obrien@gmail.com, 47558@debbugs.gnu.org
>
> > Why do you need that in the first place? The compiler should be looking
> > there by default.
>
> It may be because we have to build with clang, or it may be because of
> how homebrew installs things. Or both. I'm not sure.
That alone is worth a bug report against clang, I think.
> breton:/Users/alan>gcc -print-file-name=libgccjit.so
> libgccjit.so
>
> which isn't helpful, but again may be because gcc is actually clang.
The above means the compiler cannot find the file. Does the file's
name actually end in .so, or is it some .dynlib or some such?
Does clang support the -v switch, whereby it emits details about the
directories it searches and libraries it scans? If so, can you run
the link command with that switch and show the entire output?
next prev parent reply other threads:[~2021-04-07 11:50 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
2021-04-07 10:35 ` Andreas Schwab
2021-04-07 10:48 ` Alan Third
2021-04-07 11:50 ` Eli Zaretskii [this message]
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=83zgya9uvo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47558@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=alan@idiocy.org \
--cc=bryan.m.obrien@gmail.com \
--cc=schwab@linux-m68k.org \
/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).