From: "Johannes Grødem" <johs@ekki.no>
To: 44128@debbugs.gnu.org
Subject: bug#44128: [feature/native-comp]
Date: Wed, 14 Apr 2021 19:28:53 +0200 [thread overview]
Message-ID: <878s5kixm2.fsf@ekki.no> (raw)
In-Reply-To: <87eelri6l8.fsf@bernoul.li>
Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
>>> You mentioned that this happens because code in pdump[er].c just relies
>>> on invocation-directory and that you are wonder whether symlinks should
>>> be followed to address this.
>>>
>>> I think they should. :D
>>
>> Well I agree :)
>>
>> I believe the only question is if we want to change
>> `invocation-directory' to have the link followed or to do that in the
>> load mechanism. I guess the second has less impact.
>
> Hi all,
>
> I think this question got answered by Eli's comment on bug#46790 :)
>
> I've pushed 0c1fc9d581 that seams to work for me, please have a try.
This fixed it for me. Thanks!
--
Sent from my Emacs
next prev parent reply other threads:[~2021-04-14 17:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 21:58 bug#44128: [feature/native-comp] Jonas Bernoulli
2020-10-22 20:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-14 13:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-14 17:28 ` Johannes Grødem [this message]
2021-04-14 22:22 ` Phil Sainty
2021-04-15 6:52 ` Eli Zaretskii
2021-04-15 12:12 ` Phil Sainty
2021-04-15 12:29 ` Eli Zaretskii
2021-04-15 13:01 ` Phil Sainty
2021-04-15 13:52 ` Eli Zaretskii
2021-04-15 14:05 ` Phil Sainty
2021-04-15 14:42 ` Eli Zaretskii
2021-04-15 21:52 ` Phil Sainty
2021-04-16 6:50 ` Eli Zaretskii
2021-04-16 12:04 ` Phil Sainty
2021-04-16 12:20 ` Eli Zaretskii
2021-04-16 12:59 ` Phil Sainty
2021-04-16 13:21 ` Jonas Bernoulli
2021-04-16 15:08 ` Eli Zaretskii
2021-04-17 13:58 ` bug#44128: [feature/native-comp] When invoking a symlink to the 'emacs' binary Emacs fails to start Eli Zaretskii
2021-04-17 14:13 ` bug#44128: bug#47800: " Phil Sainty
2021-04-17 14:29 ` Eli Zaretskii
2021-04-17 15:00 ` Phil Sainty
2021-04-17 15:12 ` Eli Zaretskii
2021-04-17 15:39 ` bug#44128: " Dario Gjorgjevski
2021-04-17 15:48 ` Eli Zaretskii
2021-04-17 19:15 ` wilde
2021-04-17 19:18 ` Eli Zaretskii
2021-04-17 19:32 ` wilde
2021-04-18 8:42 ` Eli Zaretskii
2021-04-18 9:01 ` Eli Zaretskii
2021-04-18 12:24 ` wilde
2021-04-18 13:00 ` Eli Zaretskii
2021-04-19 14:37 ` Jonas Bernoulli
2021-04-19 14:52 ` Eli Zaretskii
2021-04-18 7:40 ` Phil Sainty
2021-04-18 8:09 ` bug#44128: " Eli Zaretskii
2021-04-18 3:40 ` Richard Stallman
2021-04-18 6:58 ` Eli Zaretskii
2021-04-15 10:09 ` bug#44128: symlink problem after applying commit 0c1fc9d Kent Engström
2021-04-18 7:41 ` Kent Engström
2021-04-18 16:04 ` Eli Zaretskii
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=878s5kixm2.fsf@ekki.no \
--to=johs@ekki.no \
--cc=44128@debbugs.gnu.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).