From: Andreas Fuchs <asf@boinkor.net>
To: Andrea Corallo <akrl@sdf.org>
Cc: 43137@debbugs.gnu.org, Vibhav Pant <vibhavp@gmail.com>
Subject: bug#43137: 28.0.50; [feature/native-comp] .eln path fixup confused using relative paths
Date: Tue, 1 Sep 2020 10:15:50 -0400 [thread overview]
Message-ID: <CAOHxn7wMFV7A292t1C5d+ykOn58xnJxN+SoMaVxbu8+e8xRReg@mail.gmail.com> (raw)
In-Reply-To: <xjfzh6awzcu.fsf@sdf.org>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Andrea Corallo <akrl@sdf.org> writes:
> The first is to provide the correct eln destination directory during the
> build so it can be used correctly by the logic that starts at
> loadup.el:452. This should fixup the filenames so afterwards when
> resurrecting the logic in pdumper.c can work correctly.
>
> About this there's a branch in feature/native-comp-macos-fixes (by
> Vibhav Pant Cc'ed) with a fix. See also [1]. Maybe you like to give it
> a go.
Oooh, that's a good catch. If I read the diff correctly, with a
not-only-self-contained build, it will set things up such that the
Application bundle works, but the (also installed) emacs binary won't.
A solution here might be to build two pdmp files - one for the
relocatable app bundle and one for commandline usage. I'll try to build
that.
> The other possible source of problems may be Vinvocation_directory still
> not set when we pass into pdumper.c:5270, I can't verify that as I don't
> have use macos but should be realitively easy to verify.
This makes sense too. I'll investigate when `Vinvocation_directory` gets
set. Does sound like that doesn't happen early enough, maybe we can pull
it forward a bit.
Thanks,
--
Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
next prev parent reply other threads:[~2020-09-01 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 15:11 bug#43137: 28.0.50; [feature/native-comp] .eln path fixup confused using relative paths Andreas Fuchs
2020-08-31 16:32 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-01 14:15 ` Andreas Fuchs [this message]
2020-09-01 19:32 ` Andreas Fuchs
2020-09-01 19:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 0:51 ` Andreas Fuchs
2020-09-02 4:41 ` Andreas Fuchs
2020-09-02 7:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 13:49 ` Andreas Fuchs
2020-09-26 13:51 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-02 7:59 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-02 7:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOHxn7wMFV7A292t1C5d+ykOn58xnJxN+SoMaVxbu8+e8xRReg@mail.gmail.com \
--to=asf@boinkor.net \
--cc=43137@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=vibhavp@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 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.