bitbake core-image-minimal struck at [ Initialising tasks: 44% ]

bitbake core-image-minimal struck at [ Initialising tasks: 44% ]

[Ashish]

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Hi All ,
I am trying to get an basic yocto build for qemuarm.
But the build is struck at message INITIALIZING TASK : 44%

I tried with some other machine name , removing the cache folder etc but
the behaviour remians same .

Any pointers to debug will be helpful .

Thanks ,
Ashish


[LAP] ~/yocto-build/build-folder : bitbake core-image-minimal
Parsing recipes: 100%
|##########################################################################################|
Time: 0:00:57
Parsing of 774 .bb files complete (0 cached, 774 parsed). 1326 targets, 56
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-poky-linux"
MACHINE              = "qemuarm64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.11"
TUNE_FEATURES        = "aarch64 armv8a crc"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "dunfell:78fe96f3edf981285cb9b6a0286e45f44d8b4b21"

Initialising tasks:  44% |######################################

[-- Attachment #2: Type: text/html, Size: 1579 bytes --]

Re: [poky] bitbake core-image-minimal struck at [ Initialising tasks: 44% ]

[Khem Raj]

On Tue, Oct 26, 2021 at 7:11 AM Ashish <ashishm@mvista.com> wrote:
>
> Hi All ,
> I am trying to get an basic yocto build for qemuarm.
> But the build is struck at message INITIALIZING TASK : 44%
>
> I tried with some other machine name , removing the cache folder etc but the behaviour remians same .
>
> Any pointers to debug will be helpful .

check ps output and see whats executing at this point. I wonder if its
stuck parsing some git recipe with autorev or something like that.

>
> Thanks ,
> Ashish
>
>
> [LAP] ~/yocto-build/build-folder : bitbake core-image-minimal
> Parsing recipes: 100% |##########################################################################################| Time: 0:00:57
> Parsing of 774 .bb files complete (0 cached, 774 parsed). 1326 targets, 56 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION           = "1.46.0"
> BUILD_SYS            = "x86_64-linux"
> NATIVELSBSTRING      = "universal"
> TARGET_SYS           = "aarch64-poky-linux"
> MACHINE              = "qemuarm64"
> DISTRO               = "poky"
> DISTRO_VERSION       = "3.1.11"
> TUNE_FEATURES        = "aarch64 armv8a crc"
> TARGET_FPU           = ""
> meta
> meta-poky
> meta-yocto-bsp       = "dunfell:78fe96f3edf981285cb9b6a0286e45f44d8b4b21"
>
> Initialising tasks:  44% |######################################
>
> --
> Thanks ,
> Ashish .
> 
>

Re: [poky] bitbake core-image-minimal struck at [ Initialising tasks: 44% ]

[Jose Quaresma]

[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]

If you are using an upstream hash equivalence server it will deadlock if
you have a clean cache dir.

https://lists.openembedded.org/g/openembedded-core/topic/86362510

Jose

Khem Raj <raj.khem@gmail.com> escreveu no dia terça, 26/10/2021 à(s) 16:55:

> On Tue, Oct 26, 2021 at 7:11 AM Ashish <ashishm@mvista.com> wrote:
> >
> > Hi All ,
> > I am trying to get an basic yocto build for qemuarm.
> > But the build is struck at message INITIALIZING TASK : 44%
> >
> > I tried with some other machine name , removing the cache folder etc but
> the behaviour remians same .
> >
> > Any pointers to debug will be helpful .
>
> check ps output and see whats executing at this point. I wonder if its
> stuck parsing some git recipe with autorev or something like that.
>
> >
> > Thanks ,
> > Ashish
> >
> >
> > [LAP] ~/yocto-build/build-folder : bitbake core-image-minimal
> > Parsing recipes: 100%
> |##########################################################################################|
> Time: 0:00:57
> > Parsing of 774 .bb files complete (0 cached, 774 parsed). 1326 targets,
> 56 skipped, 0 masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION           = "1.46.0"
> > BUILD_SYS            = "x86_64-linux"
> > NATIVELSBSTRING      = "universal"
> > TARGET_SYS           = "aarch64-poky-linux"
> > MACHINE              = "qemuarm64"
> > DISTRO               = "poky"
> > DISTRO_VERSION       = "3.1.11"
> > TUNE_FEATURES        = "aarch64 armv8a crc"
> > TARGET_FPU           = ""
> > meta
> > meta-poky
> > meta-yocto-bsp       = "dunfell:78fe96f3edf981285cb9b6a0286e45f44d8b4b21"
> >
> > Initialising tasks:  44% |######################################
> >
> > --
> > Thanks ,
> > Ashish .
> >
> >
>
> 
>
>

-- 
Best regards,

José Quaresma

[-- Attachment #2: Type: text/html, Size: 2817 bytes --]

Re: [poky] bitbake core-image-minimal struck at [ Initialising tasks: 44% ]

[Jose Quaresma]

[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]

Jose Quaresma via lists.yoctoproject.org <quaresma.jose=
gmail.com@lists.yoctoproject.org> escreveu no dia terça, 26/10/2021 à(s)
17:42:

> If you are using an upstream hash equivalence server it will deadlock if
> you have a clean cache dir.
>
>
Don't consider my last message, it is only true on the master branch and if
we can't connect the hash equivalence server.


> https://lists.openembedded.org/g/openembedded-core/topic/86362510
>
> Jose
>
> Khem Raj <raj.khem@gmail.com> escreveu no dia terça, 26/10/2021 à(s)
> 16:55:
>
>> On Tue, Oct 26, 2021 at 7:11 AM Ashish <ashishm@mvista.com> wrote:
>> >
>> > Hi All ,
>> > I am trying to get an basic yocto build for qemuarm.
>> > But the build is struck at message INITIALIZING TASK : 44%
>> >
>> > I tried with some other machine name , removing the cache folder etc
>> but the behaviour remians same .
>> >
>> > Any pointers to debug will be helpful .
>>
>> check ps output and see whats executing at this point. I wonder if its
>> stuck parsing some git recipe with autorev or something like that.
>>
>> >
>> > Thanks ,
>> > Ashish
>> >
>> >
>> > [LAP] ~/yocto-build/build-folder : bitbake core-image-minimal
>> > Parsing recipes: 100%
>> |##########################################################################################|
>> Time: 0:00:57
>> > Parsing of 774 .bb files complete (0 cached, 774 parsed). 1326 targets,
>> 56 skipped, 0 masked, 0 errors.
>> > NOTE: Resolving any missing task queue dependencies
>> >
>> > Build Configuration:
>> > BB_VERSION           = "1.46.0"
>> > BUILD_SYS            = "x86_64-linux"
>> > NATIVELSBSTRING      = "universal"
>> > TARGET_SYS           = "aarch64-poky-linux"
>> > MACHINE              = "qemuarm64"
>> > DISTRO               = "poky"
>> > DISTRO_VERSION       = "3.1.11"
>> > TUNE_FEATURES        = "aarch64 armv8a crc"
>> > TARGET_FPU           = ""
>> > meta
>> > meta-poky
>> > meta-yocto-bsp       =
>> "dunfell:78fe96f3edf981285cb9b6a0286e45f44d8b4b21"
>> >
>> > Initialising tasks:  44% |######################################
>> >
>> > --
>> > Thanks ,
>> > Ashish .
>> >
>> >
>>
>>
>>
>>
>
> --
> Best regards,
>
> José Quaresma
>
> 
>
>

-- 
Best regards,

José Quaresma

[-- Attachment #2: Type: text/html, Size: 3829 bytes --]

Warning: empty_var_volatile doesn't exist

[Steve]

Hello,

I would like to remove /etc/timestamp from my rootfs.
I found it is set by "rootfs_update_timestamp" as part of
ROOTFS_POSTPROCESS_COMMAND.

I did in my image recipe the following:
ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp ; "

That seems to work, no /etc/timestamp in image.
But I get the warning from do_rootfs:
"Function write_image_test_data  empty_var_volatile doesn't exist"

Did I do something wrong? I am not feeling well to ignore warnings,
especially as I am a beginner here.

Maybe allow me a second question:
I need a part of utils-linux, but won't include all the files (due to
space limitations).
I guess I need some utils-linux_%.bbappend - but what has to be in there?

Thanks, Arno (in Yocto 3.0 atm)

Re: [poky] Warning: empty_var_volatile doesn't exist

[Peter Kjellerstedt]

> -----Original Message-----
> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
> Of Steve
> Sent: den 27 oktober 2021 10:42
> To: poky@lists.yoctoproject.org
> Subject: [poky] Warning: empty_var_volatile doesn't exist
> 
> Hello,
> 
> I would like to remove /etc/timestamp from my rootfs.
> I found it is set by "rootfs_update_timestamp" as part of
> ROOTFS_POSTPROCESS_COMMAND.
> 
> I did in my image recipe the following:
> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp ; "

That should be:

ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp;"

The _remove operator will remove each word specified from the original 
variable. So in your case it would remove all "rootfs_update_timestamp" 
and all ";", which is not what you want.
> 
> That seems to work, no /etc/timestamp in image.
> But I get the warning from do_rootfs:
> "Function write_image_test_data  empty_var_volatile doesn't exist"
> 
> Did I do something wrong? I am not feeling well to ignore warnings,
> especially as I am a beginner here.
> 
> Maybe allow me a second question:
> I need a part of utils-linux, but won't include all the files (due to
> space limitations).
> I guess I need some utils-linux_%.bbappend - but what has to be in there?
> 
> Thanks, Arno (in Yocto 3.0 atm)
> 

//Peter

Re: [poky] Warning: empty_var_volatile doesn't exist

[Steve]

Thanks Peter,
>> -----Original Message-----
>> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
>> Of Steve
>> Sent: den 27 oktober 2021 10:42
>> To: poky@lists.yoctoproject.org
>> Subject: [poky] Warning: empty_var_volatile doesn't exist
>>
>> Hello,
>>
>> I would like to remove /etc/timestamp from my rootfs.
>> I found it is set by "rootfs_update_timestamp" as part of
>> ROOTFS_POSTPROCESS_COMMAND.
>>
>> I did in my image recipe the following:
>> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp ; "
>
> That should be:
>
> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp;"
>
> The _remove operator will remove each word specified from the original
> variable. So in your case it would remove all "rootfs_update_timestamp"
> and all ";", which is not what you want.


It isn't as easy as in original is like (watch the blanks)
" ... ; rootfs_update_timestamp ; >next..."

So if I do:
ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp;"
it is not removed
and if I do
ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp"
I got errors because of "; ;"

So my guess is, the original recipe with this blanks is not correct.
But how to workaround?

>>
>> That seems to work, no /etc/timestamp in image.
>> But I get the warning from do_rootfs:
>> "Function write_image_test_data  empty_var_volatile doesn't exist"
>>
>> Did I do something wrong? I am not feeling well to ignore warnings,
>> especially as I am a beginner here.
>>
>> Maybe allow me a second question:
>> I need a part of utils-linux, but won't include all the files (due to
>> space limitations).
>> I guess I need some utils-linux_%.bbappend - but what has to be in there?
>>
>> Thanks, Arno (in Yocto 3.0 atm)
>>
>
> //Peter
>

Best regards,  Arno

Re: [poky] Warning: empty_var_volatile doesn't exist

[Peter Kjellerstedt]

> -----Original Message-----
> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
> Of Steve
> Sent: den 27 oktober 2021 11:10
> To: poky@lists.yoctoproject.org
> Subject: Re: [poky] Warning: empty_var_volatile doesn't exist
> 
> Thanks Peter,
> >> -----Original Message-----
> >> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On
> Behalf
> >> Of Steve
> >> Sent: den 27 oktober 2021 10:42
> >> To: poky@lists.yoctoproject.org
> >> Subject: [poky] Warning: empty_var_volatile doesn't exist
> >>
> >> Hello,
> >>
> >> I would like to remove /etc/timestamp from my rootfs.
> >> I found it is set by "rootfs_update_timestamp" as part of
> >> ROOTFS_POSTPROCESS_COMMAND.
> >>
> >> I did in my image recipe the following:
> >> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp ; "
> >
> > That should be:
> >
> > ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp;"
> >
> > The _remove operator will remove each word specified from the original
> > variable. So in your case it would remove all "rootfs_update_timestamp"
> > and all ";", which is not what you want.
> 
> 
> It isn't as easy as in original is like (watch the blanks)
> " ... ; rootfs_update_timestamp ; >next..."
> 
> So if I do:
> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp;"
> it is not removed
> and if I do
> ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp"
> I got errors because of "; ;"
> 
> So my guess is, the original recipe with this blanks is not correct.

It was corrected in 3.2.

> But how to workaround?

I believe it should work to do:

ROOTFS_POSTPROCESS_COMMAND_remove = "rootfs_update_timestamp"

That will leave "... ; ; ..." in ROOTFS_POSTPROCESS_COMMAND, but I think 
that should be ok.

> >> That seems to work, no /etc/timestamp in image.
> >> But I get the warning from do_rootfs:
> >> "Function write_image_test_data  empty_var_volatile doesn't exist"
> >>
> >> Did I do something wrong? I am not feeling well to ignore warnings,
> >> especially as I am a beginner here.
> >>
> >> Maybe allow me a second question:
> >> I need a part of utils-linux, but won't include all the files (due to
> >> space limitations).
> >> I guess I need some utils-linux_%.bbappend - but what has to be in
> >> there?
> >>
> >> Thanks, Arno (in Yocto 3.0 atm)
> >
> > //Peter
> 
> Best regards,  Arno

//Peter