From: Andrea Corallo <akrl@sdf.org>
To: 51104@debbugs.gnu.org
Cc: larsi@gnus.org, eggert@cs.ucla.edu, andrea_corallo@yahoo.it
Subject: bug#51104: comp-tests.elc messes up after reconfiguring for different machine
Date: Mon, 12 Sep 2022 19:34:49 +0000 [thread overview]
Message-ID: <xjfedwgcrom.fsf@ma.sdf.org> (raw)
In-Reply-To: <a51593c6-330e-c4bd-090f-a22f0c6f2aba@cs.ucla.edu> (Paul Eggert via's message of "Mon, 12 Sep 2022 12:54:36 -0500")
Paul Eggert via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> On 9/12/22 10:30, Andrea Corallo wrote:
>> I believe in theory should be possible to move this computation in the
>> compile time to keep "comp-tests.elc" arch indepent if this is
>> requirement.
>
> As I understand it, .elc files are supposed to be architecture independent.
>
> Is Lars onto something when he says this should be a .eln file
> instead? I don't recall what comp-tests.el does.
comp-tests.el just tests the native compiler (in this case the ret type
prediction it does).
I guess here make check does byte-compile comp-tests.el but being the
tests executed with a non-interactive emacs this is never native compiled
afterward (it would hide the issue).
Probably the quickest and easiest fix is just to add the
`no-byte-compile' into comp-tests.el.
Andrea
next prev parent reply other threads:[~2022-09-12 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 22:59 bug#51104: comp-tests.elc messes up after reconfiguring for different machine Paul Eggert
2022-09-12 11:15 ` Lars Ingebrigtsen
2022-09-12 11:43 ` Eli Zaretskii
2022-09-12 15:30 ` Andrea Corallo
2022-09-12 17:54 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 19:34 ` Andrea Corallo [this message]
2022-09-12 20:34 ` Paul Eggert via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12 21:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 11:21 ` Lars Ingebrigtsen
2022-09-13 13:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 14:09 ` Andrea Corallo
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=xjfedwgcrom.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=51104@debbugs.gnu.org \
--cc=andrea_corallo@yahoo.it \
--cc=eggert@cs.ucla.edu \
--cc=larsi@gnus.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).