From: Andrea Corallo <akrl@sdf.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Gregory Heytings <gregory@heytings.org>,
Lars Ingebrigtsen <larsi@gnus.org>,
57849@debbugs.gnu.org
Subject: bug#57849: 29.0.50; MacOS ld warning from native compilation
Date: Fri, 16 Sep 2022 21:53:46 +0000 [thread overview]
Message-ID: <xjfo7vfasut.fsf@ma.sdf.org> (raw)
In-Reply-To: <m2o7vflbzc.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Fri, 16 Sep 2022 14:50:31 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Gregory Heytings <gregory@heytings.org> writes:
>
>>>> I cannot find anything at all about the warning on the web.
>>>
>>> There's:
>>>
>>> https://githublab.com/profile/kateinoigakukun
>>>
>>> But er where's the actual link to the patch? Confusing interface.
>>>
>>
>> There's no patch AFAICS, but the discussion is here:
>> https://githublab.com/repository/issues/chef/ffi-yajl/114
>>
>> See another similar discussion here:
>> https://github.com/ruby/ruby/pull/6193
>>
>> Apparently the solution is to use the -bundle_loader option.
>
> He writes
>
> On the other hand, -undefined dynamic_lookup is already deprecated on
> all darwin platforms except for macOS,
>
> Aha, that's interesting.
>
> so it's good time to get rid of
> the option. ld64 also provides -bundle_loader <executable> option,
> which allows to resolve symbols defined in the executable symtab while
> linking. It behaves almost the same with -undefined dynamic_lookup,
> but it makes the following changes:
>
> Require that unresolved symbols among input objects must be defined
> in the executable.
>
> I'm not sure this is true for elns. What if a function in a.eln calls a
> function F in b.eln?
This is never the case. Functions in .eln files either call functions in
Emacs core or either call functions in the same .eln file.
Andrea
next prev parent reply other threads:[~2022-09-16 21:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 5:48 bug#57849: 29.0.50; MacOS ld warning from native compilation Gerd Möllmann
2022-09-16 10:51 ` Lars Ingebrigtsen
2022-09-16 12:34 ` Gerd Möllmann
2022-09-16 12:39 ` Lars Ingebrigtsen
2022-09-16 12:44 ` Gerd Möllmann
2022-09-16 12:44 ` Gregory Heytings
2022-09-16 12:50 ` Gerd Möllmann
2022-09-16 13:05 ` Gerd Möllmann
2022-09-16 13:39 ` Gerd Möllmann
2022-09-16 13:52 ` Eli Zaretskii
2022-09-16 14:01 ` Gerd Möllmann
2022-09-16 21:53 ` Andrea Corallo [this message]
2022-09-17 4:45 ` Gerd Möllmann
2022-09-17 7:16 ` Gerd Möllmann
2022-09-17 7:31 ` Eli Zaretskii
2022-09-17 8:17 ` Gerd Möllmann
2022-09-17 8:57 ` Gerd Möllmann
2022-09-19 5:19 ` Gerd Möllmann
2024-05-18 6:30 ` 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=xjfo7vfasut.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=57849@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=gregory@heytings.org \
--cc=larsi@gnus.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 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.