all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: eggert@cs.ucla.edu
Cc: luangruo@yahoo.com, 58535@debbugs.gnu.org
Subject: bug#58535: Build failure on old GNU/Linux system
Date: Sat, 15 Oct 2022 22:06:55 +0300	[thread overview]
Message-ID: <83czas6h4g.fsf@gnu.org> (raw)
In-Reply-To: <83h7046h7x.fsf@gnu.org> (message from Eli Zaretskii on Sat, 15 Oct 2022 22:04:50 +0300)

> Cc: luangruo@yahoo.com, 58535@debbugs.gnu.org
> Date: Sat, 15 Oct 2022 22:04:50 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > Cc: 58535@debbugs.gnu.org
> > Date: Sat, 15 Oct 2022 12:01:37 -0700
> > From: Paul Eggert <eggert@cs.ucla.edu>
> > 
> > On 2022-10-15 04:24, Po Lu wrote:
> > > Right, that seems to have fixed the problem.  I'm closing this bug then,
> > > sorry for the noise.
> > 
> > No problem. On the contrary I vaguely recall running into this hassle 
> > too, and I should have fixed it then. I installed the attached.
> 
> I think we decided not to remove the cache as part of a bootstrap,
> since doing that slows down bisecting and clean builds in general,
> when the configuration and the platform didn't change.

Ignore me: that was for "FAST" bootstrap.





      reply	other threads:[~2022-10-15 19:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pmetpzmd.fsf.ref@yahoo.com>
2022-10-15  2:52 ` bug#58535: Build failure on old GNU/Linux system Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15  8:41   ` Paul Eggert
     [not found]     ` <87o7udo4i8.fsf@yahoo.com>
2022-10-15  9:03       ` Paul Eggert
2022-10-15 11:24         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 19:01           ` Paul Eggert
2022-10-15 19:04             ` Eli Zaretskii
2022-10-15 19:06               ` Eli Zaretskii [this message]

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=83czas6h4g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58535@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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 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.