From: Mauricio Collares <mauricio@collares.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45462@debbugs.gnu.org
Subject: bug#45462: 28.0.50; [feature/native-comp] trailing backslashes in comp-eln-load-path are required but shouldn't
Date: Thu, 14 Jan 2021 10:56:22 -0300 [thread overview]
Message-ID: <87czy7pqpl.fsf@collares.org> (raw)
In-Reply-To: <xjfwnx3kvs6.fsf@sdf.org>
Andrea Corallo <akrl@sdf.org> writes:
> Hi Mauricio,
>
> ee53560c8c should fix this, please have a try.
>
> Thanks for reporting.
>
> Andrea
Hi Andrea,
As I mentioned before, previous tests worked fine. However, while
debugging #45854, I saw this problem again today. A minimized testcase:
* file1.el:
(require 'file2)
(provide 'file1)
* file2.el:
(advice-add 'top-level :before 'identity)
(provide 'file2)
Then the command
emacs --batch -Q --eval "(add-to-list 'load-path \"~\")" --eval "(setq comp-eln-load-path '(\"~/eln\"))" -f batch-native-compile ~/file1.el
compiles file1 to ~/eln/28.0.50-host-arch/ (as expected) but compiles
the trampoline to ~/eln28.0.50-host-arch/.
Best,
Mauricio
next prev parent reply other threads:[~2021-01-14 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-27 15:00 bug#45462: 28.0.50; [feature/native-comp] trailing backslashes in comp-eln-load-path are required but shouldn't Mauricio Collares
2020-12-27 17:23 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-05 0:35 ` Mauricio Collares
2021-01-05 9:34 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 13:56 ` Mauricio Collares [this message]
2021-01-14 14:17 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-14 21:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-18 12:17 ` Mauricio Collares
2021-01-18 12:36 ` akrl--- 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
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=87czy7pqpl.fsf@collares.org \
--to=mauricio@collares.org \
--cc=45462@debbugs.gnu.org \
--cc=akrl@sdf.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).