From: Eric Sunshine Date: Mon, 21 Nov 2022 05:12:09 GMT Subject: Re: git can not be built for s390x since update to git-2.38.0 Message-ID: In-Reply-To: <4657a19c-89c3-2237-9e6b-db897a492072@opensuse.org> [cc:+git; taking this back to the mailing list so others can weigh in] On Wed, Nov 9, 2022 at 1:38 AM Sarah Julia Kriesch wrote: > > Gesendet: Sonntag, 06. November 2022 um 21:42 Uhr > > Von: "Eric Sunshine" > > > > On Sun, Nov 6, 2022 at 2:18 PM Sarah Julia Kriesch > > wrote: > > > We have also identified this week, that chainlint.pl --stats says "0 > > > tests". That can explain the empty output. > > > > > > ~/rpmbuild/BUILD/git-2.38.1/t> /usr/bin/perl chainlint.pl --stats > > > --emit-all chainlinttmp/tests > > > total: 0 workers, 0 scripts, 0 tests, 0 errors, 0.01s/0.01s (wall/user) > > > > Was `--stats` added for debugging this issue, or is that somehow part > > of your build process? > > > Yes. We tried to debug that manually. Therefore, we have added the --stats. > > > What is the content of the "chainlinttmp/tests" file? Is it empty? > > > It is empty. > > > It is quite curious that it reports 0 scripts. It should report 1 > > script even if chainlinttmp/file is empty. This might point a finger > > at File::Glob::bsd_glob() returning an empty list for some reason, or > > the problem could be a failure with Perl "ithreads". Do you happen to know if Perl is built with "ithreads" on your platform, and if so, is "ithread" support working? The empty "chainlinttmp/tests" file also sounds suspicious. If you haven't already done so, I would recommend following the advice in [1] and running each command individually which Makefile would have run; this might allow you to isolate the problematic command or shell construct if such exists. [1]: https://lore.kernel.org/git/CAPig+cS184iKk6icG6ML=X+6Ng=fJyfic8izFyp1hT40cChm4g@mail.gmail.com/