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.

>