From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58625@debbugs.gnu.org
Subject: bug#58625: bug-gnu-emacs@gnu.org
Date: Fri, 21 Oct 2022 09:17:23 +0200 [thread overview]
Message-ID: <920562AA-16EB-4501-A649-F218CF60CA6B@univie.ac.at> (raw)
In-Reply-To: <CADwFkmm-kC71SSX7LPjPboBQ_Ao1gWTYvO_6JZupFsabB3uNqQ@mail.gmail.com>
> Am 20.10.2022 um 23:13 schrieb Stefan Kangas <stefankangas@gmail.com>:
>
> Konrad Podczeck <konrad.podczeck@univie.ac.at> writes:
>
>>> Am 19.10.2022 um 13:47 schrieb Stefan Kangas <stefankangas@gmail.com>:
>>>
>>> Konrad Podczeck <konrad.podczeck@univie.ac.at> writes:
>>>
>>>> In fact, /the folder "Users/konradpodczeck/.emacs.d/eln-cache/“ exists
>>>> but is and remains empty.
>>>
>>> Did you build --with-native-compilation?
>>
>> Yes, I did.
>
> This may be related to the recently fixed Bug#58637.
Yes, with the latest master branch, everything is fine.
One final question: Now, e.g., latex.el., from the folder …/elpa/auctex-13.1.4, compiles into an eln-file, however, deleting afterwards the files latex.el and latex.elc from the folder …/elpa/auctex-13.1.4 results in an auctex with losses functionality. On the contrary, if, e.g., startup.el.gz and startup.elc are deleted from Applications/Emacs/Contents/Resources /lisp, the Emacs.app continues to be full functional. Can it be that such differences in the results of native compilation occur?
Thanks,
Konrad
>
> Could you retry using the latest master branch?
next prev parent reply other threads:[~2022-10-21 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 10:14 bug#58625: bug-gnu-emacs@gnu.org Konrad Podczeck
2022-10-19 11:01 ` Stefan Kangas
2022-10-19 11:23 ` Konrad Podczeck
2022-10-19 11:47 ` Stefan Kangas
2022-10-19 12:05 ` Konrad Podczeck
2022-10-20 21:13 ` Stefan Kangas
2022-10-21 7:17 ` Konrad Podczeck [this message]
2022-10-21 7:43 ` Stefan Kangas
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=920562AA-16EB-4501-A649-F218CF60CA6B@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=58625@debbugs.gnu.org \
--cc=stefankangas@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.