From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: contovob@tcd.ie, rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: master 9e94509 3/3: Generate info/dir directly from any org sources
Date: Wed, 05 Jan 2022 19:09:55 +0200 [thread overview]
Message-ID: <83czl69kik.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRHgu3WB8qRMY7uCB4ZzKX=urqt2ed5FCo8Tu+AuthH-g@mail.gmail.com> (message from Philipp Stephani on Wed, 5 Jan 2022 17:58:47 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Wed, 5 Jan 2022 17:58:47 +0100
> Cc: Glenn Morris <rgm@gnu.org>, Emacs developers <emacs-devel@gnu.org>
>
> Am Sa., 6. März 2021 um 21:16 Uhr schrieb Basil L. Contovounesios
> <contovob@tcd.ie>:
> >
> > Glenn Morris <rgm@gnu.org> writes:
> >
> > > Glenn Morris wrote:
> > >
> > >> I'll ask the help-make list...
> > >
> > > They suggested something, I applied it in f476e282d2.
> > > Based on what you said previously about -j1, I'm not sure it will make a
> > > difference for you.
> >
> > And yet it works fine with -j8 and -j16 here, thanks!
> >
>
> The "multiple target patterns" issue still occasionally happens for me
> (on the emacs-28 branch) even with f476e282d2. It's very difficult to
> reproduce and only seems to happen occasionally with 'make
> bootstrap-clean' under specific circumstances. Does anybody have a
> recipe for a more robust fix? Maybe "export MAKEFLAGS=-O" before
> running anything else?
As mentioned back then, using -O is a non-starter.
next prev parent reply other threads:[~2022-01-05 17:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210304184723.8249.29253@vcs0.savannah.gnu.org>
[not found] ` <20210304184725.15B2320E1B@vcs0.savannah.gnu.org>
2021-03-05 12:03 ` master 9e94509 3/3: Generate info/dir directly from any org sources Basil L. Contovounesios
2021-03-05 19:17 ` Glenn Morris
2021-03-06 11:51 ` Basil L. Contovounesios
2021-03-06 13:49 ` Lars Ingebrigtsen
2021-03-06 14:09 ` Basil L. Contovounesios
2021-03-06 14:16 ` Mattias Engdegård
2021-03-06 14:51 ` Eli Zaretskii
2021-03-06 15:31 ` Basil L. Contovounesios
2021-03-06 15:51 ` Eli Zaretskii
2021-03-06 17:21 ` Basil L. Contovounesios
2021-03-06 17:23 ` Andreas Schwab
2021-03-06 17:37 ` Basil L. Contovounesios
2021-03-06 18:10 ` Andreas Schwab
2021-03-06 18:34 ` Basil L. Contovounesios
2021-03-06 17:28 ` Glenn Morris
2021-03-06 17:41 ` Basil L. Contovounesios
2021-03-06 17:47 ` Glenn Morris
2021-03-06 19:12 ` Glenn Morris
2021-03-06 20:15 ` Basil L. Contovounesios
2022-01-05 16:58 ` Philipp Stephani
2022-01-05 17:09 ` Eli Zaretskii [this message]
2021-03-06 20:40 ` 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=83czl69kik.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=rgm@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).