From: akrl--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 45934@debbugs.gnu.org
Cc: Davide Restivo <davide.restivo@yahoo.it>
Subject: bug#45934: native-comp - Dylib ID of ELN files not optimal
Date: Sun, 17 Jan 2021 12:36:09 +0000 [thread overview]
Message-ID: <xjfy2grzqo6.fsf@sdf.org> (raw)
In-Reply-To: <EDAEF3DD-6B4E-4ED9-A7B8-8FB4F236DF42@yahoo.it> (davide restivo's message of "Sun, 17 Jan 2021 11:13:25 +0100")
"davide.restivo--- via \"Bug reports for GNU Emacs, the Swiss army knife
of text editors\"" <bug-gnu-emacs@gnu.org> writes:
[...]
> Since the tmp directory is stripped out and replaced with the
> destination directory, as you can see, all of the ELN files ends up with
> the same dylib ID, and this is not allowed on macOS. My suggestion here
> would be to add the 'install_name' [2] flag to gcc during the ELN files
> compilation replacing the 'fake.so' with the original .eln filename.
>
> Thanks and regards,
> Davide
>
>
> [1] https://github.com/daviderestivo/homebrew-emacs-head
> [2] gcc -o libdummy.dylib -install_name ${PREFIX}/lib/libdummy.dylib
Hi Davide,
I'm really ignorant on MacOS so I'll comment for what I can. I had a
look to the GCC doc [1] but I could not figure out if '-install_name' is
an option that goes to the compiler or the linker (nor I know what this
dylib ID exactly is). If the flag is routed to the linker we should be
able to add it but only when libgccjit >= 9 is used.
Could you run a random compilation of something using '-install_name'
but adding also '-v' and report the console output so we can see where
the driver is routing the flag?
Thanks
Andrea
[1] https://gcc.gnu.org/onlinedocs/gcc/Darwin-Options.html
next prev parent reply other threads:[~2021-01-17 12:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDAEF3DD-6B4E-4ED9-A7B8-8FB4F236DF42.ref@yahoo.it>
2021-01-17 10:13 ` bug#45934: native-comp - Dylib ID of ELN files not optimal davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-17 12:36 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-17 16:48 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-17 20:06 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-23 16:13 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-24 19:37 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28 21:59 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-29 7:09 ` Eli Zaretskii
2021-01-29 8:52 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-30 8:18 ` davide.restivo--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-11 16:00 ` xgutter--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-30 12:32 ` Lars Ingebrigtsen
2021-08-02 14:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-04 6:55 ` Lars Ingebrigtsen
2021-08-04 18:11 ` Alan Third
2021-08-05 10:54 ` Lars Ingebrigtsen
2021-08-05 19:00 ` Alan Third
2021-08-06 10:49 ` Lars Ingebrigtsen
2021-08-06 16:37 ` Alan Third
2021-08-07 9:52 ` Lars Ingebrigtsen
2021-08-07 9:57 ` Lars Ingebrigtsen
2021-08-07 10:25 ` Lars Ingebrigtsen
2021-08-07 13:11 ` Alan Third
2021-08-09 12:20 ` Lars Ingebrigtsen
2021-08-22 17:18 ` Davide Restivo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-22 19:40 ` Davide Restivo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-22 21:18 ` Alan Third
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=xjfy2grzqo6.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45934@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=davide.restivo@yahoo.it \
/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).