On Sun, 2022-06-05 at 04:26 +0200, Jacob Kroon wrote: > On Sat, 4 Jun 2022, 19:40 Richard Purdie, > <[email protected]> wrote: > > On Sat, 2022-06-04 at 17:12 +0200, Jacob Kroon wrote: > > > On 6/4/22 16:55, Khem Raj wrote: > > > > > > > > > > > > On Sat, Jun 4, 2022 at 6:23 AM Richard Purdie > > > > <[email protected] > > > > <mailto:[email protected]>> wrote: > > > > > > > > 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 > > > > anywhere > > > > > > else except Ubuntu 18.04? > > > > > > > > > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14096 > > > > <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14096> > > > > > > > > > > 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: > > > > > > > > > > > > https://git.savannah.gnu.org/cgit/make.git/commit/?id=9bb994e8 > > > > 319c2b153cd3d6d61e2c2882895e7c3a > > > > > > > > <https://git.savannah.gnu.org/cgit/make.git/commit/?id=9bb994e > > > > 8319c2b153cd3d6d61e2c2882895e7c3a> > > > > > > > > https://git.savannah.gnu.org/cgit/make.git/commit/?id=4762480a > > > > e9cb8df4878286411f178d32db14eff0 > > > > > > > > <https://git.savannah.gnu.org/cgit/make.git/commit/?id=4762480 > > > > ae9cb8df4878286411f178d32db14eff0> > > > > > > > > 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 > > > > distros... > > > > > > > > > > > > Make perhaps does not have many complex dependency needs so it > > > > might not > > > > be as bad > > > > > > > > > > My master build is already building make-native due to a > > > dependency from > > > glibc, since 2018: > > > > > > https://git.openembedded.org/openembedded-core/commit/?id=0cd89e4af625941f8ab8c033f72f900a2979b304 > > > > > > 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- > > native now. > > > Would it be a bad idea to add make-native to DEPENDS depending on > whether the host version of make is new enough or not ? Would it > break sstate cache reuse in some way ?
We can't have a conditional dependency like that, the task checksums as implemented today wouldn't work and it would break ssttate reuse. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#166590): https://lists.openembedded.org/g/openembedded-core/message/166590 Mute This Topic: https://lists.openembedded.org/mt/91540379/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
