From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>,
48079@debbugs.gnu.org
Subject: bug#48079: Temporary files while building after native-comp merge
Date: Sun, 02 May 2021 21:36:04 +0000 [thread overview]
Message-ID: <xjf5z00x1h7.fsf@sdf.org> (raw)
In-Reply-To: <CADwFkmkr9FwgXfp7rHZV1OOsHA58YQ_y=EuvHEb24u+C95o7Qg@mail.gmail.com> (Stefan Kangas's message of "Sun, 2 May 2021 05:12:24 -0500")
Stefan Kangas <stefan@marxist.se> writes:
> tags 48079 - patch
> thanks
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Stefan Kangas <stefan@marxist.se> writes:
>>
>>> But perhaps the fix is as simple as:
>>>
>>> diff --git a/.gitignore b/.gitignore
>>> index fcbc9cd7f4..e27ebe36d0 100644
>>> --- a/.gitignore
>>> +++ b/.gitignore
>>> @@ -135,6 +135,7 @@ src/gl-stamp
>>> *.dll
>>> *.core
>>> *.elc
>>> +*.elc[0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z][0-9A-Za-z]
>>> *.eln
>>> *.o
>>> *.res
>>
>> Sounds like a good idea to me. (But add a comment about what these
>> files are.)
>
> Thanks.
>
> But now I am seeing that some of these files have not been deleted in my
> tree:
>
> lisp/emacs-lisp/comp.elcivrXZS
> lisp/window.elc9aaVMg
>
> This might be because I interrupted the build process at some point; I
> don't know.
>
> These files don't get removed when I run extraclean or bootstrap. So if
> we just ignore them there is a risk that these files will slowly build
> up over time.
>
> Perhaps we should also make sure they get cleaned up when building, as
> in the attached.
I'm not sure is correct to do that in compile-clean, if there's really a
problem IMO we should isolate it and debug, IIUC having this in
compile-clean could just mask it.
Andrea
next prev parent reply other threads:[~2021-05-02 21:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 11:10 bug#48079: Temporary files while building after native-comp merge Stefan Kangas
2021-04-28 12:10 ` Eli Zaretskii
2021-04-28 12:30 ` Eli Zaretskii
2021-04-28 13:14 ` Stefan Kangas
2021-04-28 19:27 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-28 21:26 ` Stefan Kangas
2021-04-29 5:14 ` Eli Zaretskii
2021-04-29 8:19 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 9:20 ` Eli Zaretskii
2021-04-29 10:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-02 23:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 17:14 ` Eli Zaretskii
2022-01-06 16:10 ` Andrea Corallo
2022-01-06 16:30 ` Glenn Morris
2022-01-06 16:48 ` Eli Zaretskii
2022-01-06 17:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-07 16:30 ` Andrea Corallo
2022-01-14 15:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-29 11:22 ` Stefan Kangas
2021-04-29 8:18 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-02 8:09 ` Lars Ingebrigtsen
2021-05-02 10:12 ` Stefan Kangas
2021-05-02 10:18 ` Lars Ingebrigtsen
2021-05-02 21:36 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-05-05 8:35 ` Lars Ingebrigtsen
2021-05-05 12:11 ` Eli Zaretskii
2021-05-05 12:47 ` Lars Ingebrigtsen
2021-05-05 14:01 ` Eli Zaretskii
2021-05-05 14:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-06 9:15 ` Lars Ingebrigtsen
2021-05-06 10:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-28 19:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-24 12:36 ` Lars Ingebrigtsen
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=xjf5z00x1h7.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48079@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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.