From: xiliuya via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63062@debbugs.gnu.org
Subject: bug#63062: 29.0.90; configure.ac : what's different `--with-native-compilation=aot' and `--with-native-compilation=yes' ?
Date: Tue, 25 Apr 2023 18:31:41 +0800 [thread overview]
Message-ID: <87wn20dv87.fsf@aliyun.com> (raw)
In-Reply-To: <83cz3swfja.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 25 Apr 2023 12:44:19 +0800
>> From: xiliuya via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> When I compiled the packages in the same system environment using the
>> '--with-native-compilation=aot' and the '--with-native-compilation=yes'
>> respectively, file lists differ only by a few `.ELN'
>>
>> For example, 'lisp/avoid.el' is only compiled to '.elc', does not compile all
>> Lisp files as '.eln'.
>
> I seem to be unable to reproduce this. I see all the *.el files
> compiled to *.eln under this option.
>
> Where (in which sub-directory of the build tree) did you look for the
> *.eln files you expected to be produced by the build? Also, if you
> try this in a freshly-cloned repository, does it work then?
Hello,Eli Zaretskii:
Sorry for the late reply.
I tried compiling many times to find the
problem. I tested it at archlinux.
This is because I didn't clean up the files generated by the last
compilation. I am very sorry for the wrong question.
--
xiliuya :)
next prev parent reply other threads:[~2023-04-25 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 4:44 bug#63062: 29.0.90; configure.ac : what's different `--with-native-compilation=aot' and `--with-native-compilation=yes' ? xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 8:07 ` Eli Zaretskii
2023-04-25 10:31 ` xiliuya via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-25 12:34 ` 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=87wn20dv87.fsf@aliyun.com \
--to=bug-gnu-emacs@gnu.org \
--cc=63062@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=xiliuya@aliyun.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 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).