Re: #yocto #sdk #yocto #sdk


Monsees, Steven C (US)
 

Nope, just validated...

I build the my kernel image clean and the eSDK image right after, cache should be good, no ?

Not sure how to go about resolving... it occurs on the back end of the eSDK installation. I can actually go to the install and build the kernel image under the umbrella of the eSDK and it builds/runs correctly...

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of Khem Raj
Sent: Thursday, March 4, 2021 12:18 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #sdk

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.


if you have AUTOREVs e.g. can be problematic, and also using TIME/DATE in recipes which can interfere

On 3/4/21 5:13 AM, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
Is there a list of certain classes that might interfere with the
ability of the eSDK to lock down the configuratiuon ?

Thanks,

Steve

*From:* yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>
*On Behalf Of *Monsees, Steven C (US) via lists.yoctoproject.org
*Sent:* Tuesday, March 2, 2021 3:26 PM
*To:* yocto@lists.yoctoproject.org
*Subject:* [yocto] #yocto #sdk

*_External Email Alert_*

*This email has been sent from an account outside of the BAE Systems
network.*

Please treat the email with caution, especially if you are requested
to click on a link, decrypt/open an attachment, or enable macros.  For
further information on how to spot phishing, access “Cybersecurity
OneSpace Page” and report phishing by clicking the button “Report
Phishing” on the Outlook toolbar.

I still appear to be having an issue with the SXT SDK install…

Building for zeus/x86_64 Intel based platform…

I build my kernel image clean, fully functional…

Standard SDK builds clean and appears functional…

Ext SDK builds clean, but on install I am still seeing Error below…

(1)What is it comparing  between unhash/task hash ?, more sig issues ?

(2)What is meant by “This is usually due to missing setscene tasks” ?

(3)In the local.conf under the SDK they set :

SSTATE_MIRRORS += " file://universal/(.*) <file://universal/(.*)>
file://universal-4.9/\1 <file://universal-4.9/1>
file://universal-4.9/(.*) <file://universal-4.9/(.*)>
file://universal-4.8/\1 <file://universal-4.8/1>"

Under sdk-extra.conf I set :

SSTATE_MIRRORS += file://.*
file:///ede/tms/yocto/zeus/sstate_cache/PATH
<file://.*%20file:/ede/tms/yocto/zeus/sstate_cache/PATH>

My SSTATE_MIRRIOR is based off the clean builds I mentioned above, is
this the correct procedure ?

I am trying to figure out how best to debug this issue, it is
occurring on the post install, and everything pretty much appears in place.

Steve

14:43 smonsees@yix490038
/disk0/scratch/smonsees/yocto/workspace_3/builds2/sbcb-default/tmp/dep
loy/sdk>./limws-glibc-x86_64-aiox_orange-corei7-64-toolchain-ext-3.0.4
.sh

LIMWS (BAE LIMWS base distro) Extensible SDK installer version 3.0.4

====================================================================

Enter target directory for SDK (default: ~/limws_sdk):
/disk0/scratch/smonsees/testSDK

You are about to install the SDK to "/disk0/scratch/smonsees/testSDK".
Proceed [Y/n]? Y

Extracting
SDK...................................................................
...........done

Setting it up...

Extracting buildtools...

Preparing build system...

Parsing recipes: 100%
|#####################################################################
|######################|
Time: 0:01:32

Initialising tasks: 100%
|#####################################################################
|###################|
Time: 0:00:04

Checking sstate mirror object availability: 100%
|################################################################| Time:
0:00:03

ERROR: Task quilt-native.do_fetch attempted to execute unexpectedly

Task
/disk0/scratch/smonsees/testSDK/layers/poky/meta/recipes-support/libur
cu/liburcu_0.11.1.bb:do_populate_sysroot,
unihash
cdb08644b85fa162bd9f88cb00113fe3193cc347e39e33e8f405f9c23f60c601,
taskhash
cdb08644b85fa162bd9f88cb00113fe3193cc347e39e33e8f405f9c23f60c601

Task
/disk0/scratch/smonsees/testSDK/layers/poky/meta/recipes-devtools/pyth
on/python3_3.7.8.bb:do_packagedata,
unihash
925a72cbe872aad09bd3fbbe74ed1c944e9c19a732e120feae5c4784e6330d4f,
taskhash
925a72cbe872aad09bd3fbbe74ed1c944e9c19a732e120feae5c4784e6330d4f

.

.

.

This is usually due to missing setscene tasks. Those missing in this
build were:

<<appears to list every recipe under ./testSDK/layers directory here>>




Join yocto@lists.yoctoproject.org to automatically receive all group messages.