From: Live System User <nyc4bos@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33049@debbugs.gnu.org
Subject: bug#33049: 27.0.50; Uncompiled .el files after make -- intentional?
Date: Tue, 16 Oct 2018 05:39:45 -0400 [thread overview]
Message-ID: <87in22dyce.fsf@aol.com> (raw)
In-Reply-To: <83sh17rsnr.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 15 Oct 2018 21:06:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Live System User <nyc4bos@aol.com>
>> Date: Mon, 15 Oct 2018 13:41:31 -0400
>>
>> Recently, I noticed after a git pull and make, some
>> files are now not being byte-compiled
>>
>> -rw-rw-r--. 1 liveuser liveuser 181985 Oct 13 22:54 tramp.el
>> -rw-rw-r--. 1 liveuser liveuser 217141 Oct 9 14:55 tramp.elc
>
> I cannot reproduce it here. My tramp.elc has a later timestamp than
> tramp.el.
>
>> So what triggers a byte-compilation when doing a `make'?
>
> Time stamps, of course.
>
>> What caused tramp.el to not be recompiled after a
>> subsequent `make'?
>
> No idea. How about running "make -d" and examining the (voluminous)
> output, where it talks about tramp.el?
OK, I';; try doing that.
>
>> (I normally do a `make TAGS' if that matters, FWIW).
>
> You mean, you run _only_ "make TAGS"? That's insufficient, I think.
The exact command I use is:
make TAGS CFLAGS='-O2 -march=native'
```````` Thanks.
next prev parent reply other threads:[~2018-10-16 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 17:41 bug#33049: 27.0.50; Uncompiled .el files after make -- intentional? Live System User
2018-10-15 18:06 ` Eli Zaretskii
2018-10-16 9:39 ` Live System User [this message]
2018-10-16 14:54 ` 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=87in22dyce.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=33049@debbugs.gnu.org \
--cc=eliz@gnu.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).