From: Boran Car <boran.car@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Chris Packham via Libc-help <libc-help@sourceware.org>,
Chris Packham <judge.packham@gmail.com>
Subject: Re: Build hangs on stdio-common for glibc-2.30-67-g4748829f86a458b76642f3e98b1d80f7b868e427
Date: Mon, 18 Sep 2023 18:06:01 +0200 [thread overview]
Message-ID: <CAPa+MXkb4LEWBZWzn9Bhs=TZeo8xqYkrTdMiN5ToaJmkFLOqjA@mail.gmail.com> (raw)
In-Reply-To: <87sf7bbtbd.fsf@oldenburg.str.redhat.com>
I don't think so, Googling has been quite difficult - lead me to a
Stack Overflow question that prompted me to reach out to the mailing
list where I found a mention of a GitHub issue. I can confirm that it
just works (tm) with an earlier Make version, v4.2, and I have a
simple Nix shell derivation to prove it (yeah, I know Nix + Buildroot,
go figure...).
shell.nix:
```
let pkgs = import { };
in pkgs.mkShell {
hardeningDisable = [ "all" ];
nativeBuildInputs = [ pkgs.gcc7 pkgs.gnumake42 ];
CC="${pkgs.gcc7}/bin/gcc";
CXX="${pkgs.gcc7}/bin/g++";
}
```
There's definitely interest in fixing this, at least from my side, but
I do need handholding through the build-system. If a Makefile can be
back-ported, even better. There's still interest in pre 2.31 glibcs
out there, and Buildroot and crosstools-NG were definitely not made to
build their own Make as part of the process.
On Mon, Sep 18, 2023 at 1:43 PM Florian Weimer <fweimer@redhat.com> wrote:
>
> * 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
>
next prev parent reply other threads:[~2023-09-18 16:06 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
2023-09-18 16:06 ` Boran Car [this message]
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='CAPa+MXkb4LEWBZWzn9Bhs=TZeo8xqYkrTdMiN5ToaJmkFLOqjA@mail.gmail.com' \
--to=boran.car@gmail.com \
--cc=fweimer@redhat.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).