On Wed, 3 Jul 2024 at 10:09, Sundeep KOKKONDA <
[email protected]> wrote:

>
> I ran both with 'bitbake -c install rust' which runs a complete build up
> to install task, and then checked that rustdoc in image/ is different
> between them. The other tasks aren't relevant, and you can ignore lack of
> package/ etc.
>
> You need to check the difference in content of rustc-1.75.0-src/ (this is
> where the build runs and intermediate artefacts are), and maybe
> temp/log.do_install will give clues about rustdoc as well.
>
> Hi Alex,
>
> I am checking the build artifacts generated and finding the probable
> reasons to identify the issue. While looking onto *.../temp/* I've seen a
> log - '*log.do_recipe_qa_setscene*', as per my understanding this task
> ensure that the build system can reuse previous build results to avoid
> unnecessary recompilation and to speed up the build process and which needs
> sharing of *sstate*. This log only seen in '*build-64-2*' directory (not
> in '*build-64*' dir).
>
> Also, I've checked my previous builds where sstate not shared and this
> task was not executed. In may case, I made multiple builds and the issue
> not reproduced w/o sharing sstate. Can you check local.conf settings the
> sstate is disabled? and when will the '*do_recipe_qa_setscene'  *task
> execute w/o sstate sharing?
>

 Hello Sundeep,

recipe_qa task is only used for QA checks on the recipe and has no
influence on what gets built and installed. The actual build and
installation happens in do_install task, and both tarballs have a built
tree where do_install was fully executed, with results going into image/
(specifically, that directory has two different rustdoc executables).

So you can ignore any other task, regardless of whether it's fulfilled from
sstate or not. The key pieces in the tarballs are the content of image/
(where rustdoc differs), temp/log.do_install (the log for build and
installation which may give clues to where things diverge), and the content
of rustc-1.75.0-src/. The challenging part for you is to narrow this down
to the specific point where the two builds diverge.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201466): 
https://lists.openembedded.org/g/openembedded-core/message/201466
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to