From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Build failure with --with-x-toolkit=no
Date: Sat, 30 Mar 2024 10:36:28 +0100 [thread overview]
Message-ID: <cbb19456-c27b-4745-8f61-59dfc583040f@gmx.at> (raw)
In-Reply-To: <8634s9fh28.fsf@gnu.org>
> You could then do "git -fdxn", which would show you the files that
> perhaps need to be removed, without actually removing them.
When I do git clean -fdxn it, probably correctly, does not descend into
the build directories but just tells me that it would remove them as a
whole (like the info directory, for example).
The great problem I never managed to fix appropriately is that when
removing a build directory as a whole, I also remove previous versions
of emacs builds which, however, I occasionally need to track down in
which version an error appeared first. So I'd need a regexp to tell git
clean which files it should delete for making builds succeed cleanly and
which ones to keep for future forensics. Having executables and object
files in the same directory is not helpful in this regard.
martin
next prev parent reply other threads:[~2024-03-30 9:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 9:19 Build failure with --with-x-toolkit=no martin rudalics
2024-03-27 11:19 ` Po Lu
2024-03-28 9:44 ` martin rudalics
2024-03-28 10:25 ` Eli Zaretskii
2024-03-29 7:58 ` martin rudalics
2024-03-29 10:50 ` Eli Zaretskii
2024-03-30 9:36 ` martin rudalics [this message]
2024-03-30 9:44 ` Andreas Schwab
2024-03-31 8:30 ` martin rudalics
2024-03-31 8:59 ` Andreas Schwab
2024-04-01 9:10 ` martin rudalics
2024-04-01 9:20 ` Andreas Schwab
2024-04-02 7:49 ` martin rudalics
2024-04-02 16:53 ` Andreas Schwab
2024-04-03 8:24 ` martin rudalics
2024-03-30 9:54 ` tomas
2024-03-31 8:31 ` martin rudalics
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=cbb19456-c27b-4745-8f61-59dfc583040f@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).