public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Chris Packham via Libc-help <libc-help@sourceware.org>
Cc: Boran Car <boran.car@gmail.com>,
	 Chris Packham <judge.packham@gmail.com>
Subject: Re: Build hangs on stdio-common for glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427
Date: Mon, 18 Sep 2023 13:43:18 +0200	[thread overview]
Message-ID: <87sf7bbtbd.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAFOYHZABd=rMRufzdvR+mR_O_+KQb48yNTgnwTYuEWJsM+NcMg@mail.gmail.com> (Chris Packham via Libc-help's message of "Mon, 18 Sep 2023 20:16:06 +1200")

* Chris Packham via Libc-help:

>> My questions are:
>> - Are there any pointers where I should go looking for what's the
>> cause of the re-executions and how to prevent them?
>> - Is there anything I can use from subsequent glibc Makefiles? Was an
>> issue discovered with the target computation?
>>
>
> There is a pretty good explanation of the problem and some workarounds at
> https://github.com/crosstool-ng/crosstool-ng/issues/1932#issuecomment-1528139734
>
> Using a newer glibc is probably the best solution. If you really need to
> use that specific version then downgrading your local version of make is
> another option.

Has this reported anywhere as a make or glibc issue?  I don't
immediately recall how we fixed this in glibc 2.31.

Thanks,
Florian


  reply	other threads:[~2023-09-18 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 18:53 Boran Car
2023-09-17 19:21 ` Boran Car
2023-09-18  8:16 ` Chris Packham
2023-09-18 11:43   ` Florian Weimer [this message]
2023-09-18 16:06     ` Boran Car
2023-09-19 21:08       ` Chris Packham
2023-10-01 11:48         ` Boran Car

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=87sf7bbtbd.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=boran.car@gmail.com \
    --cc=judge.packham@gmail.com \
    --cc=libc-help@sourceware.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. 
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).