On Thu, 2022-06-09 at 14:44 +0200, Martin Jansa wrote:
> On Mon, Jun 6, 2022 at 2:02 PM Alexander Kanavin <alex.kana...@gmail.com> 
> wrote:
> > Signed-off-by: Alexander Kanavin <a...@linutronix.de>
> > ---
> >  .../{perlcross_1.3.7.bb => perlcross_1.4.bb}  |  2 +-
> >  .../perl/files/perl-configpm-switch.patch     |  2 +-
> >  .../perl/files/perl-dynloader.patch           |  2 +-
> >  .../perl/files/perl-rdepends.txt              | 49 ++++++++++++-------
> >  .../perl/{perl_5.34.1.bb => perl_5.36.0.bb}   |  2 +-
> >  5 files changed, 35 insertions(+), 22 deletions(-)
> >  rename meta/recipes-devtools/perl-cross/{perlcross_1.3.7.bb => 
> > perlcross_1.4.bb} (92%)
> >  rename meta/recipes-devtools/perl/{perl_5.34.1.bb => perl_5.36.0.bb} (99%)
> > 
> 
> 
> Have anyone else seen perl.do_install getting stuck with this new shiny 
> version as well?
> 
>  690770 martin      20   0 10020  3700  3196 S   0.0  0.0  0:00.00 │        
> └─ /bin/sh 
> /OE/build/poky/build-st/tmp/work/x86_64-linux/perl-native/5.36.0-r0/temp/run.do_install.690768
>  690771 martin      20   0 99860  1948  1364 S   0.0  0.0  0:00.00 │          
>  └─ make -j 40 
> DESTDIR=/OE/build/poky/build-st/tmp/work/x86_64-linux/perl-native/5.36.0-r0/image
>  install
>  690816 martin      20   0   99M  3340  1428 R 102.1  0.0  3h06:44 │          
>     └─ make install.man 

I've seen perl and the kernel hang in make for some versions, I did try
and put a warning about the known Fedora issue. Was this with the
recent make-native dependency added? If so that would indicate it is
potentially a bug in the current make version :(

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#166782): 
https://lists.openembedded.org/g/openembedded-core/message/166782
Mute This Topic: https://lists.openembedded.org/mt/91575167/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to