From: Chris Packham <judge.packham@gmail.com>
To: Boran Car <boran.car@gmail.com>
Cc: libc-help@sourceware.org
Subject: Re: Build hangs on stdio-common for glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427
Date: Mon, 18 Sep 2023 20:16:06 +1200 [thread overview]
Message-ID: <CAFOYHZABd=rMRufzdvR+mR_O_+KQb48yNTgnwTYuEWJsM+NcMg@mail.gmail.com> (raw)
In-Reply-To: <CAPa+MXmUEuKbuO+ZeJqRJYNRuUg_QDVO3kWqA=QbfETRK-s7Rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]
Hi Boran
On Mon, 18 Sep 2023, 6:54 AM Boran Car via Libc-help, <
libc-help@sourceware.org> wrote:
> While using crosstools-NG and Buildroot, and even manually going into
> the folder and executing make, I would end up with the build hanging
> at
>
> `make -d subdir=stdio-common -C stdio-common ..=../ subdir_lib`
>
> I'm using GNU Make 4.4.1.
>
> I modified the Makefile to print out tracing information when hitting
> stdio-common and re-ran it and I get make itself re-executing the
> target, never finishing, despite the target already being built.
> Here's a very short and snipped output of the trace, because it's very
> noisy:
> ```
> Considering target file
>
> '/home/boran/git/buildroot-2020.02.3/output/build/glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427/build/bits/stdio_lim.d'.
> File
> '/home/boran/git/buildroot-2020.02.3/output/build/glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427/build/bits/stdio_lim.d'
> was considered already.
> Re-executing[48]: make -d subdir=stdio-common -C stdio-common ..=../
> subdir_lib
> ```
>
> I can also modify the Makefile to skip stdio-common/subdir_lib and
> will then get stuck in stdio-common/others, and modifying that to skip
> it will get stuck on stdio-common/subdir_install. Those are the only 3
> issues, and I usually have to let them run on the first try and skip
> on subsequent tries. With those changes in place, the glibc builds
> successfully.
>
> 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.
>
next prev parent reply other threads:[~2023-09-18 8:16 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 [this message]
2023-09-18 11:43 ` Florian Weimer
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='CAFOYHZABd=rMRufzdvR+mR_O_+KQb48yNTgnwTYuEWJsM+NcMg@mail.gmail.com' \
--to=judge.packham@gmail.com \
--cc=boran.car@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).