On 10/23/23 9:16 PM, Kelly (US), Matt via lists.yoctoproject.org wrote:

On Oct 19, 2023, at 10:13 PM, Mark Hatle <[email protected]> wrote:


I am using Ubuntu 22.04 (as well as 18.04) and I'm not able to replicate this 
failure.

The way I configured was:

mkdir 2023.1
cd 2023.1
repo init -u https://github.com/Xilinx/yocto-manifests.git
repo sync
. ./setupsdk build
MACHINE=vpk120-versal bitbake core-image-minimal

If this matches what you did (or if not, if you can try it) and you get the same result, 
then something is likely wrong with "xsct".  Can you check the work logs in 
plm-firmware and see if there are any other error messages above this?


I was not following this flow. I was just following the flow in the 
README.building.md. The issue here was that our base RHEL 9.2 did not have 
xterm installed by default. It seems a bit strange that xsct relies on xterm, 
but oh well. There is a small chance that it depends on another package that 
installed before xterm as well. I was simply following the required packages 
for PetaLinux from top to bottom and it began working when I hit xterm.

You don't need to follow the flow above, but that is the flow we are testing. So further from that flow the more likelihood you will find issues. (Ones are real bugs and should be fixed.)

As for requiring xterm, this seems broken to me. Was the only think you installed on RHEL 9.2 'xterm' or where there other dependencies brought in?

Another (far better) solution is adding DEPENDS += “xt-native” to the recipe. 
Would you accept a patch for that?

Potentially, but I need to find a way to reproduce it so I can be sure this is enough.

--Mark

--Matt Kelly





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5274): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5274
Mute This Topic: https://lists.yoctoproject.org/mt/102060990/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to