-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EDM-G-IMX8MP Yocto build fails #38
Comments
Hi @burtbick Thanks for the feedback. It is recommended to use our docker container, dockerfile as below: Or use the virtual machines we built. Thanks, |
Thanks Ray,
I need to double check but I believe that it was the kirkstone branch.
I'll take a loot at the docker container and also maybe the VM, although probably the docker container will run faster.
Burt
…________________________________
From: Ray Chang ***@***.***>
Sent: Tuesday, June 6, 2023 2:00 AM
To: TechNexion/tn-imx-yocto-manifest ***@***.***>
Cc: burt burtbicksler.com ***@***.***>; Mention ***@***.***>
Subject: Re: [TechNexion/tn-imx-yocto-manifest] EDM-G-IMX8MP Yocto build fails (Issue #38)
Hi @burtbick<https://github.com/burtbick>
Thanks for the feedback.
I'm not sure which branch you use, but I have no problem using the kirkstone_5.15.y-stable branch.
It is recommended to use our docker container, dockerfile as below:
https://github.com/TechNexion/meta-tn-imx-bsp/blob/kirkstone_5.15.71-2.2.0-stable/tools/container/dockerfile
Or use the virtual machines we built.
https://download.technexion.com/development_resources/development_tools/vm/Build_Env_Ubuntu_x64_20.04_vmware-20221202.zip
Thanks,
Ray
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYT7RNIHAPFKHRIMANRJSLXJ3BQ5ANCNFSM6AAAAAAY244LRM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi Ray,
I had hit a snag trying to use the VM, but got side tracked with some other tasks so was just getting back to it.
The file name says vmware, but it appears to be a Virtual Box VM file. In any case the conversion tool for vmware chokes on the extracted file.
The latest version of VirtualBox also refuses to load the extracted file.
So, two questions, am I correct that it is actually a VirtualBox VM? If so, will it only work with the specific version of VirtualBox mentioned?
The version I currently have installed is just a couple of versions newer.
Note I tried downloading the VM a second time just in case it somehow had gotten corrupted but that didn't make any difference.
For the Docker configuration is there a specific doc describing the process for generating images for the TechNexion dev board embedded Linux builds and not for Android?
Thanks,
Burt
…________________________________
From: Ray Chang ***@***.***>
Sent: Tuesday, June 6, 2023 2:00 AM
To: TechNexion/tn-imx-yocto-manifest ***@***.***>
Cc: burt burtbicksler.com ***@***.***>; Mention ***@***.***>
Subject: Re: [TechNexion/tn-imx-yocto-manifest] EDM-G-IMX8MP Yocto build fails (Issue #38)
Hi @burtbick<https://github.com/burtbick>
Thanks for the feedback.
I'm not sure which branch you use, but I have no problem using the kirkstone_5.15.y-stable branch.
It is recommended to use our docker container, dockerfile as below:
https://github.com/TechNexion/meta-tn-imx-bsp/blob/kirkstone_5.15.71-2.2.0-stable/tools/container/dockerfile
Or use the virtual machines we built.
https://download.technexion.com/development_resources/development_tools/vm/Build_Env_Ubuntu_x64_20.04_vmware-20221202.zip
Thanks,
Ray
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYT7RNIHAPFKHRIMANRJSLXJ3BQ5ANCNFSM6AAAAAAY244LRM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I was going to try the 6.1.14 version of VirtualBox listed in the PDF but I cannot install that on Ubuntu 22.04. And right now I don't have a machine set up with one of the versions that 6.1.14 will install on.
I have 6.1.44 VirtualBox installed and when I run VBoxManage import on the VM-TN-DEV.ova file I get the following error (also happens from the GUI).
Interpreting /media/burtbicksler/TechNexionVM/Build_Env_Ubuntu_x64_20.04-20221202/VM-TN-DEV.ova...
VBoxManage: error: Error in (line 154) -- Invalid value 'WAS' in ***@***.*** attribute.
VBoxManage: error: /home/vbox/tinderbox/build-VBox-6.1/out/out/debian/builddir/obj/VBoxAPIWrap/ApplianceWrap.cpp[407] (virtual nsresult ApplianceWrap::Interpret())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ApplianceWrap, interface IAppliance, callee IAppliance
VBoxManage: error: Context: "Interpret" at line 501 of file VBoxManageAppliance.cpp
So any suggestions other than setting up a machine with the older version of Ubuntu?
Thanks,
Burt
…________________________________
From: Ray Chang ***@***.***>
Sent: Tuesday, June 6, 2023 2:00 AM
To: TechNexion/tn-imx-yocto-manifest ***@***.***>
Cc: burt burtbicksler.com ***@***.***>; Mention ***@***.***>
Subject: Re: [TechNexion/tn-imx-yocto-manifest] EDM-G-IMX8MP Yocto build fails (Issue #38)
Hi @burtbick<https://github.com/burtbick>
Thanks for the feedback.
I'm not sure which branch you use, but I have no problem using the kirkstone_5.15.y-stable branch.
It is recommended to use our docker container, dockerfile as below:
https://github.com/TechNexion/meta-tn-imx-bsp/blob/kirkstone_5.15.71-2.2.0-stable/tools/container/dockerfile
Or use the virtual machines we built.
https://download.technexion.com/development_resources/development_tools/vm/Build_Env_Ubuntu_x64_20.04_vmware-20221202.zip
Thanks,
Ray
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYT7RNIHAPFKHRIMANRJSLXJ3BQ5ANCNFSM6AAAAAAY244LRM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi Ray,
I was able to come up with a solution for the issue with VirtualBox not importing the VM. I had to extract the files from the .ova, and then edit the config file to remove the line related to the audio driver.
Of course that changed the file signature but I resolved that and was able to import the VM.
But unfortunately I found that the machine I had set up doesn't appear to be able to setup the BIOS to support virtual machines.
So, I'm hoping that there is a good document for using the docker implementation for creating images for the dev board linux OS. Not Android.
If not then I'll have to set up another machine that can run the VM, but I don't have any other small form factors and I was going to take this with me on an upcoming trip to work on our project.
Thanks,
Burt
…________________________________
From: Ray Chang ***@***.***>
Sent: Tuesday, June 6, 2023 2:00 AM
To: TechNexion/tn-imx-yocto-manifest ***@***.***>
Cc: burt burtbicksler.com ***@***.***>; Mention ***@***.***>
Subject: Re: [TechNexion/tn-imx-yocto-manifest] EDM-G-IMX8MP Yocto build fails (Issue #38)
Hi @burtbick<https://github.com/burtbick>
Thanks for the feedback.
I'm not sure which branch you use, but I have no problem using the kirkstone_5.15.y-stable branch.
It is recommended to use our docker container, dockerfile as below:
https://github.com/TechNexion/meta-tn-imx-bsp/blob/kirkstone_5.15.71-2.2.0-stable/tools/container/dockerfile
Or use the virtual machines we built.
https://download.technexion.com/development_resources/development_tools/vm/Build_Env_Ubuntu_x64_20.04_vmware-20221202.zip
Thanks,
Ray
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYT7RNIHAPFKHRIMANRJSLXJ3BQ5ANCNFSM6AAAAAAY244LRM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @burtbick Docker is recommended, which is the easiest way to do it. The steps can be referred to: BR, |
Thanks Ray,
I don't know why I didn't spot that one. I had found one that was for building for Android.
Burt
…________________________________
From: Ray Chang ***@***.***>
Sent: Monday, June 12, 2023 3:49 AM
To: TechNexion/tn-imx-yocto-manifest ***@***.***>
Cc: burt burtbicksler.com ***@***.***>; Mention ***@***.***>
Subject: Re: [TechNexion/tn-imx-yocto-manifest] EDM-G-IMX8MP Yocto build fails (Issue #38)
Hi @burtbick<https://github.com/burtbick>
Docker is recommended, which is the easiest way to do it.
The steps can be referred to:
https://developer.technexion.com/docs/building-an-image-in-docker-container
BR,
Ray
—
Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACYT7RMWVTNCZT43E3C2DW3XK3CZTANCNFSM6AAAAAAY244LRM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I followed the instructions shown in this repo for the Yocto build. Specifically the Yocto Xwayland build.
Specifically bitbake imx-image-full
Hit an error during the build with building the following:
edm_yocto/build-xwayland-edm-g-imx8mp/tmp/work/armv8a-poky-linux/assimp/5.2.4-r0/git/code/AssetLib/glTF/glTFImporter.cpp
Failure is:
edm_yocto/build-xwayland-edm-g-imx8mp/tmp/work/armv8a-poky-linux/assimp/5.2.4-r0/git/code/AssetLib/glTF/glTFAsset.inl:760:23: error: 'type_str' may be used uninitialized in this function [-Werror=maybe-uninitialized]
edm_yocto/build-xwayland-edm-g-imx8mp/tmp/work/armv8a-poky-linux/assimp/5.2.4-r0/git/code/AssetLib/glTF/glTFAsset.inl:761:13: error: 'component_type' may be used uninitialized in this function [-Werror=maybe-uninitialized]
..
cc1plus: all warnings being treated as errors
So of course this caused the build to terminate.
5.2.4-r0/git/code/AssetLib/glTF2/glTF2Importer.cpp
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
ERROR: Task (edm_yocto/sources/meta-imx/meta-sdk/recipes-graphics/vulkan/assimp_5.2.4.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4570 tasks of which 0 didn't need to be rerun and 1 failed.
What might I have missed in the configuration, and what is the easiest way to correct this issue?
Thanks,
Burt
The text was updated successfully, but these errors were encountered: