On Sat, 2022-06-04 at 17:12 +0200, Jacob Kroon wrote:
On 6/4/22 16:55, Khem Raj wrote:
My master build is already building make-native due to a dependency from
On Sat, Jun 4, 2022 at 6:23 AM Richard Purdie
On Sat, 2022-06-04 at 13:36 +0100, Richard Purdie via
lists.yoctoproject.org <http://lists.yoctoproject.org> wrote:
> On Sat, 2022-06-04 at 13:51 +0200, Alexander Kanavin wrote:
> > Here's something I didn't think of before. Has this occurred
> > else except Ubuntu 18.04?
> I'm struggling to get the data out from the old builds, one mentions
> ubuntu1604, there is an ubuntu1804 on both x86 and arm hosts.
> It is possible this is an ubuntu specific make issue or a make bug.
Ubuntu 18.04 uses make 4.1 which is old (Oct 2014).
I noticed these patches from 2016:
I think we may want to mandate a modern make for both this class of
issues and also perhaps for better loadavg support to keep load under
control on the autobuilders.
I'm torn, on the one hand we need to test the distros people use, on
the other we do need to remove sources of intermittent issues. I think
this bug must be some issue with make itself.
Adding a make-native dependency to perl would "hurt" people on modern
Make perhaps does not have many complex dependency needs so it might not
be as bad
glibc, since 2018:
Don't know if that dependency is still valid though.
It is a fair point. We may as well add it to perl/perl-native. Centos7
still has make 3.82 but I think we now already require buildtools
tarball there so we could probably drop the glibc dependency on make-