From: Andrea Corallo <akrl@sdf.org>
To: "Nicolas Bértolo" <nicolasbertolo@gmail.com>
Cc: 41329@debbugs.gnu.org
Subject: bug#41329: [feature/native-comp] The Makefile only checks for .elc files.
Date: Sat, 16 May 2020 16:55:17 +0000 [thread overview]
Message-ID: <xjfeerjddl6.fsf@sdf.org> (raw)
In-Reply-To: <CAFnS-O=cK6dRqNEYaEDm8wm92DbMNuuAwYPBijqEUVyE5Zy5dA@mail.gmail.com> ("Nicolas Bértolo"'s message of "Sat, 16 May 2020 13:15:40 -0300")
Nicolas Bértolo <nicolasbertolo@gmail.com> writes:
> There is a problem with the build system for .eln files. The Makefile
> only has a
> target creating *.elc files.
Yes the main reason for that is that the Makefile is not aware of which
files are lexical and can be compiled and which are dynamic and can't.
> This means that if you use Emacs to
> change an .el
> file and you set it up to byte-compile .el files on save you will
> never
> recompile the .eln files.
I'm not sure I understand. I you mean that manually byte-compiling a
file prevents the .eln compilation to happen if make is invoked
afterwards then yes. But make should be used.
> This can also be reproduced if you press C-c on a terminal that is
> native-compiling. The .eln file will not be produced, but the .elc
> will be in
> the filesystem and `make` will not try to native-compile the file
> again.
I don't think so, the .elc is renamed with their final filename after
the .eln has been produced to prevent exactly that.
This build system arrangement is till we have dynamic scope compilation
and we can clean it up.
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-05-16 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 16:15 bug#41329: [feature/native-comp] The Makefile only checks for .elc files Nicolas Bértolo
2020-05-16 16:55 ` Andrea Corallo [this message]
2020-05-16 17:45 ` Nicolas Bértolo
2020-05-16 18:19 ` Andrea Corallo
2020-08-31 20:54 ` 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=xjfeerjddl6.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=41329@debbugs.gnu.org \
--cc=nicolasbertolo@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.