[yocto] Getting error when i build an image after starting the toaster
Hello, I'm Dhanya,currently working to build an image using toaster. But the image is getting build successfully but at the last in toaster message i'm getting the error as " *ERROR: Target_File matching query does not exist*." The steps i followed is: $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev python3-subunit mesa-common-dev zstd liblz4-tool file locales $ sudo locale-gen en_US.UTF-8 $ mkdir distro $ cd distro $ repo init -u https://github.com/nxp-qoriq/yocto-sdk.git -b mickledore -m ls-6.1.55-2.2.0_distro.xml $ repo sync $ source distro-setup-env -m ls1012afrwy $ source toaster start $ bitbake ls-image-main This above steps i followed because it for my layerscape board.But i tried to build core-image-minimal from poky directory as well but still i got the same error. Error is: ERROR: Target_File matching query does not exist. Traceback (most recent call last): File "/home/dhanyalakshmi/distro/sources/poky/bitbake/lib/bb/ui/toasterui.py", line 408, in main buildinfohelper.store_target_package_data(event) File "/home/dhanyalakshmi/distro/sources/poky/bitbake/lib/bb/ui/buildinfohelper.py", line 1364, in store_target_package_data self.orm_wrapper.save_target_file_information(self.internal_state['build'], target, filedata) File "/home/dhanyalakshmi/distro/sources/poky/bitbake/lib/bb/ui/buildinfohelper.py", line 562, in save_target_file_information parent_obj = Target_File.objects.get(target = target_obj, path = parent_path, inodetype = Target_File.ITYPE_DIRECTORY) File "/home/dhanyalakshmi/.local/lib/python3.10/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/home/dhanyalakshmi/.local/lib/python3.10/site-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( orm.models.Target_File.DoesNotExist: Target_File matching query does not exist. ERROR: expected string or bytes-like object Traceback (most recent call last): File "/home/dhanyalakshmi/distro/sources/poky/bitbake/lib/bb/ui/toasterui.py", line 362, in main buildinfohelper.scan_image_artifacts() File "/home/dhanyalakshmi/distro/sources/poky/bitbake/lib/bb/ui/buildinfohelper.py", line 1782, in scan_image_artifacts real_image_name = re.sub(r'^defaultpkgname', image_target.target, File "/usr/lib/python3.10/re.py", line 209, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object WARNING: Return value is 2 I'm unable to understand this,like is a problem with toaster itself? Is their anything that i could do to resolve this issue. Does this relates to image not getting build successfully? Please help me to resolve this Hoping for the reply. Thank You. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63129): https://lists.yoctoproject.org/g/yocto/message/63129 Mute This Topic: https://lists.yoctoproject.org/mt/106150470/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Strange errors while executing poky/meta/recipes-devtools/gcc/gcc-cross_13.2.bb using scarthgap release
Hello People,
Thank you very much for helping me with uninative.
This command does it for time being (as said): INHERIT:remove = “uninative”
I fixed a few issues furthermore (my own mess).
But interesting enough, I have another package issue which popped up
(the last obstacle before building .cpio):
ERROR: cracklib-native-2.9.11-r0 do_compile: oe_runmake failed
ERROR: cracklib-native-2.9.11-r0 do_compile:
ExecutionError('/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/run.do_compile.628699',
1, None, None)
ERROR: Logfile of failure stored in:
/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/log.do_compile.628699
I even have no idea what the purpose of cracklib-native package is?
Should I disable it (if not important) in local.conf?
The .log. (cracklib-native.log) file is attached to this email.
Zee
___
On Thu, May 16, 2024 at 5:58 PM Khem Raj wrote:
>
> We need a new uninative tarball generated with gcc14 for f40 so there might
> be issues like you are seeing due to that. You can disable uninative
> temporarily in your build and see if that works for the moment
>
> On Thu, May 16, 2024 at 8:39 AM Ross Burton via lists.yoctoproject.org
> wrote:
>>
>>
>>
>> > On 16 May 2024, at 16:31, Zoran via lists.yoctoproject.org
>> > wrote:
>> > The full log (full_log.txt) is attached to this @, as per Ur request
>> > (lot of stuff, echt!).
>>
>> From your log:
>>
>> WARNING: Host distribution "fedora-40" has not been validated with this
>> version of the build system; you may possibly experience unexpected
>> failures. It is recommended that you use a tested distribution.
>>
>> This is saying that Fedora 40 has not been validated and you may experience
>> unexpected failures.
>>
>> Later in the log:
>>
>> pzstd:
>> /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/lib/libstdc++.so.6:
>> version `CXXABI_1.3.15' not found (required by pzstd)
>>
>> That is the sort of unexpected failure you can expect when using Fedora 40,
>> because it has not been validated.
>>
>> This is an incompatibility with Fedora 40 and uninative, so until this is
>> resolved you can disable uninative with this in your local.conf:
>>
>> INHERIT:remove = “uninative”
>>
>> Ross
>>
>>
Sstate summary: Wanted 20 Local 0 Mirrors 0 Missed 20 Current 2384 (0% match, 99% complete)0
Initialising tasks: 100% |###| Time: 0:00:05
NOTE: Executing Tasks
ERROR: cracklib-native-2.9.11-r0 do_compile: oe_runmake failed
ERROR: cracklib-native-2.9.11-r0 do_compile: ExecutionError('/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/run.do_compile.628699', 1, None, None)
ERROR: Logfile of failure stored in: /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/log.do_compile.628699
Log data follows:
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc', 'bit-64', 'x86_64-linux', 'common']
| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4
| make all-recursive
| make[1]: Entering directory '/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/build'
| Making all in m4
| make[2]: Entering directory '/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/build/m4'
| make[2]: Nothing to be done for 'all'.
| make[2]: Leaving directory '/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/build/m4'
| Making all in lib
| make[2]: Entering directory '/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/build/lib'
| /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../git/src/lib -I.. -I. -I.. -I../../git/src/lib -DIN_CRACKLIB '-DDEFAULT_CRACKLIB_DICT="/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/recipe-sysroot-native/usr/share/cracklib/pw_dict"' -Wall -isystem/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/recipe-sysroot-native/usr/include -isystem/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/recipe-sysroot-native/usr/include -O2 -pipe -c -o packlib.lo ../../git/src/lib/packlib.c
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../git/src/lib -I.. -I. -I.. -I../../git/src/lib -DIN_CRACKLIB -DDEFAULT_CRACKLIB_DICT=\"/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/recipe-sysroot-native/usr/share/cracklib/pw_dict\" -
Re: [yocto] Strange errors while executing poky/meta/recipes-devtools/gcc/gcc-cross_13.2.bb using scarthgap release
You're most likely missing this fix:
https://git.openembedded.org/openembedded-core/commit/?id=914128f6bd988cde278e087fb9457a0c70c7e5ec
On Fri, May 17, 2024 at 12:47 PM Zoran via lists.yoctoproject.org
wrote:
>
> Hello People,
>
> Thank you very much for helping me with uninative.
>
> This command does it for time being (as said): INHERIT:remove = “uninative”
>
> I fixed a few issues furthermore (my own mess).
>
> But interesting enough, I have another package issue which popped up
> (the last obstacle before building .cpio):
>
> ERROR: cracklib-native-2.9.11-r0 do_compile: oe_runmake failed
> ERROR: cracklib-native-2.9.11-r0 do_compile:
> ExecutionError('/home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/run.do_compile.628699',
> 1, None, None)
> ERROR: Logfile of failure stored in:
> /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/log.do_compile.628699
>
> I even have no idea what the purpose of cracklib-native package is?
>
> Should I disable it (if not important) in local.conf?
>
> The .log. (cracklib-native.log) file is attached to this email.
>
> Zee
> ___
>
> On Thu, May 16, 2024 at 5:58 PM Khem Raj wrote:
> >
> > We need a new uninative tarball generated with gcc14 for f40 so there might
> > be issues like you are seeing due to that. You can disable uninative
> > temporarily in your build and see if that works for the moment
> >
> > On Thu, May 16, 2024 at 8:39 AM Ross Burton via lists.yoctoproject.org
> > wrote:
> >>
> >>
> >>
> >> > On 16 May 2024, at 16:31, Zoran via lists.yoctoproject.org
> >> > wrote:
> >> > The full log (full_log.txt) is attached to this @, as per Ur request
> >> > (lot of stuff, echt!).
> >>
> >> From your log:
> >>
> >> WARNING: Host distribution "fedora-40" has not been validated with this
> >> version of the build system; you may possibly experience unexpected
> >> failures. It is recommended that you use a tested distribution.
> >>
> >> This is saying that Fedora 40 has not been validated and you may
> >> experience unexpected failures.
> >>
> >> Later in the log:
> >>
> >> pzstd:
> >> /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/lib/libstdc++.so.6:
> >> version `CXXABI_1.3.15' not found (required by pzstd)
> >>
> >> That is the sort of unexpected failure you can expect when using Fedora
> >> 40, because it has not been validated.
> >>
> >> This is an incompatibility with Fedora 40 and uninative, so until this is
> >> resolved you can disable uninative with this in your local.conf:
> >>
> >> INHERIT:remove = “uninative”
> >>
> >> Ross
> >>
> >>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63131): https://lists.yoctoproject.org/g/yocto/message/63131
Mute This Topic: https://lists.yoctoproject.org/mt/106133618/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] packages not generated in output folder
On 16 May 2024, at 20:28, SIMON BABY via lists.yoctoproject.org wrote: > > Hello, > > I am building some applications in 5.15.0-102-generic #112~20.04.1-Ubuntu. My > yocto recipes aeh building successfully but I am unable to see any package > folders under the tmp directory. I see only log files under temp are created. > Nothing else. Can I know if I am missing any configuration? > > tmp/work/cortexa5t2hf-neon-vfpv4-poky-linux-gnueabi/marvell-umsd/3.0.7-r0$ ls > -ll > total 12 > drwxr-xr-x 2 sbaby sbaby 12288 May 16 12:26 temp > > This is valid for other recipes as well. > > /build/tmp/work/cortexa5t2hf-neon-vfpv4-poky-linux-gnueabi/libgcc/11.4.0-r0$ > ls > temp If a recipe is pulled from sstate (because it has already been built) or if you have rm_work enabled then that’s expected behaviour. You only have a package/ directory in the work tree if the recipe was literally just re-packaged and rm_work hasn’t deleted it. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63132): https://lists.yoctoproject.org/g/yocto/message/63132 Mute This Topic: https://lists.yoctoproject.org/mt/106141357/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Strange errors while executing poky/meta/recipes-devtools/gcc/gcc-cross_13.2.bb using scarthgap release
On 17 May 2024, at 11:13, Zoran Stojsavljevic wrote: > ERROR: Logfile of failure stored in: > /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/log.do_compile.628699 If you look at the log file: | ../../git/src/lib/packlib.c:554:40: error: passing argument 1 of ‘HwmsHostToBigEndian’ from incompatible pointer type [-Wincompatible-pointer-types] Remember how Fedora 40 is unsupported? If you want to use Fedora 40 then you’ll need to join in with the effort to support GCC 14.1, which involves fixing problems like this. If you don’t want to do that, then use a supported host distribution. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63133): https://lists.yoctoproject.org/g/yocto/message/63133 Mute This Topic: https://lists.yoctoproject.org/mt/106133618/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Strange errors while executing poky/meta/recipes-devtools/gcc/gcc-cross_13.2.bb using scarthgap release
> Remember how Fedora 40 is unsupported? If you want to use > Fedora 40 then you’ll need to join in with the effort to support GCC 14.1, > which involves fixing problems like this. > > If you don’t want to do that, then use a supported host distribution. I have to give you credit for this one. I will try to apply an external patch for gcc 14 as per Martin's advice, and see what I can do furthermore. I have been with Fedora since 2012 (Fedora 14), and I have not once, not twice, but quite a few times serious issues with Fedora. Fedora is a test distro for RHELs. I did not understand this till recently. And also for kernel.org . Well. Learning in the meantime also ArchLinux (alternative to it is an Ubuntu, I also used it for a couple (maybe 4) of years in parallel with Fedora ). ___ Allow me to try the proposed patch, and see how it goes! Thank you, Zee ___ On Fri, May 17, 2024 at 12:52 PM Ross Burton wrote: > > On 17 May 2024, at 11:13, Zoran Stojsavljevic > wrote: > > ERROR: Logfile of failure stored in: > > /home/vuser/projects2/yocto/yocto_test2/bbb-yocto/poky/build/tmp/work/x86_64-linux/cracklib-native/2.9.11/temp/log.do_compile.628699 > > If you look at the log file: > > | ../../git/src/lib/packlib.c:554:40: error: passing argument 1 of > ‘HwmsHostToBigEndian’ from incompatible pointer type > [-Wincompatible-pointer-types] > > > Remember how Fedora 40 is unsupported? If you want to use Fedora 40 then > you’ll need to join in with the effort to support GCC 14.1, which involves > fixing problems like this. > > If you don’t want to do that, then use a supported host distribution. > > Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63134): https://lists.yoctoproject.org/g/yocto/message/63134 Mute This Topic: https://lists.yoctoproject.org/mt/106133618/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Strange errors while executing poky/meta/recipes-devtools/gcc/gcc-cross_13.2.bb using scarthgap release
Hi Zoran, On 5/17/24 1:28 PM, Zoran Stojsavljevic wrote: Remember how Fedora 40 is unsupported? If you want to use Fedora 40 then you’ll need to join in with the effort to support GCC 14.1, which involves fixing problems like this. If you don’t want to do that, then use a supported host distribution. I have to give you credit for this one. I will try to apply an external patch for gcc 14 as per Martin's advice, and see what I can do furthermore. I have been with Fedora since 2012 (Fedora 14), and I have not once, not twice, but quite a few times serious issues with Fedora. Fedora is a test distro for RHELs. I did not understand this till recently. And also for kernel.org . Well. Learning in the meantime also ArchLinux (alternative to it is an Ubuntu, I also used it for a couple (maybe 4) of years in parallel with Fedora ). I've been daily running Fedora but I'm always updating as soon there is a new one available... which means I never get official support for building the current Yocto release. I only use kas containers to build which is in a way pretty useful because then most colleagues would build through this container as well, abstract their local distro and everybody benefits from a more reusable/reused sstate-cache. There are also CROPS container IIRC but kas works for me and we use it for layer setup, so two features in the same tool is a nice to have. But by all means, if you can and want to help supporting newer releases of Fedora/, send patches so others benefit from it :) Good luck and looking forward to seeing patches :) Cheers, Quentin -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63135): https://lists.yoctoproject.org/g/yocto/message/63135 Mute This Topic: https://lists.yoctoproject.org/mt/106133618/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
