Re: [yocto] sd-bus.h not found even with DEPENDS += "systemd"
Without digging into the details, it sounds very very much like the most of
your problems are caused by handcrafting a Makefile which is not cross
compile aware and probably has multiple other issues. Therefore I strongly
suggest to use a build system like autotools, cmake or meson. You can find
an introduction to a cmake-based setup here: https://youtu.be/NmPta5w6P70
Greetz
Am So., 27. Sept. 2020 um 14:42 Uhr schrieb Bel Hadj Salem Talel <
bhsta...@gmail.com>:
> Hi,
>
> A response came only to me :
>
> Hey Bel,
>
> Please remove the libsystemd from your host. It will cause host
> contamination.
>
> You need to tell in your makefile where make can find include path and lib
> path
>
> Normally it should work
>
> Include: -I${STAging_incdir}
> -L for ld path
>
>
> Cheers
>
> So I added
>
> EXTRA_OEMAKE += "-I${STAGING_INCDIR}
> to fix the systemd include error.
>
> But I still get the error of :
>
>
> /media/talel/data/menzu-zeus/menzu/tmp/work/aarch64-poky-linux/wirepas-sink-tool/1.0-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux/../../libexec/aarch64-poky-linux/gcc/aarch64-poky-linux/9.2.0/ld:
> c-mesh-api/lib/build/mesh_api_lib.a: error adding symbols: file in wrong
> format
>
> I don't know what is the problem.
> Help me on this please.
>
> Thanks for your support.
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50847): https://lists.yoctoproject.org/g/yocto/message/50847
Mute This Topic: https://lists.yoctoproject.org/mt/77141718/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: Private: Re: [yocto] Information about Yocto Dunfell components version #dunfell
Well if it's not there, then it's not there. If something is not provided by a recipe, then it obviously has no defined version. Please note though that package/recipe names are not directly comparable between distributions like Ubuntu and the Yocto project ecosystem, as the names might differ slightly. Example: libtiff seems to be just "tiff". http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/libtiff/tiff_4.1.0.bb?h=dunfell Am Di., 1. Sept. 2020 um 12:55 Uhr schrieb Yocto_user < avinashyadav9...@gmail.com>: > Thanks Josef Holzmayr-Khosh Amoz for the link, but still few components > version is missing i.e. > gdkpixbuf > libjpeg > libtiff > openexr > stb-image > swscale all these are missing. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50421): https://lists.yoctoproject.org/g/yocto/message/50421 Mute This Topic: https://lists.yoctoproject.org/mt/76553512/21656 Mute #dunfell: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/dunfell Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Information about Yocto Dunfell components version #dunfell
Insert the package names into http://layers.openembedded.org/layerindex/branch/dunfell/recipes and see for yourself :) Greetz Am Di., 1. Sept. 2020 um 12:22 Uhr schrieb Yocto_user < avinashyadav9...@gmail.com>: > Hi All, > > I read the Dunfell release notes but couldn't find the version detail of > following components: > bzip2 > cairo > faad2 > fontconfig > freetype > gdkpixbuf > libav > libffi > libjpeg > libogg > libpng > libtiff > libvorbis > libxcursor > openexr > openssl > pango > pixman > stb-image > swscale > theora > x264 > zlib > Please give me the version detail of these components, we are planning to > use dunfell but before that we needed the version detail of all these > components in Yocto. > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50420): https://lists.yoctoproject.org/g/yocto/message/50420 Mute This Topic: https://lists.yoctoproject.org/mt/76553173/21656 Mute #dunfell: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/dunfell Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Help with yocto poky quick start
Howdy! Its a long shot, but are you also using WSL2 on the Windows 10 Host? In that case, downloads into a VirtualBox VM can be corrupted, see https://www.virtualbox.org/ticket/19695 Greetz Am Mi., 26. Aug. 2020 um 08:41 Uhr schrieb Brendan Simon (SEPL) : > > Hi Erik, > > Nope. It's ot a HTML file. It is (they are) archives with a > files/directories for m4 sources. > > $ find -name "m4*" > ./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c > ./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c > ./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206 > ./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616 > > $ find -name "m4*" | xargs file > ./m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c: > gzip compressed data, max compression, from Unix, original size 9789440 > ./m4-1.4.18.tar.gz_bad-checksum_e64407f9097a607b4463e0c82d898c19b0a3bfd2199d30337b5464d8b416e59c: > gzip compressed data, max compression, from Unix, original size 9789440 > ./m4-1.4.18.tar.gz_bad-checksum_d8a6ce0c8a97f9f13af9d15d72e4e398daf24ceba4afa4c6925314c39bd81206: > gzip compressed data, max compression, from Unix, original size 9789440 > ./m4-1.4.18.tar.gz_bad-checksum_b295109d6ddd3c387b794fb6e4b4dfe31d42991a6a537bd92b1a385c2ed3b616: > gzip compressed data, max compression, from Unix, original size 9789440 > > $ tar ztvf > m4-1.4.18.tar.gz_bad-checksum_6a1537c79ea613aa70849d8f1f7eeb5a5dbbea3a9527d4aea33a1c8a88e80b9c > | head > drwxrwxr-x 0/0 0 2016-12-31 17:37 m4-1.4.18/ > -rw-rw-r-- 0/0 195907 2016-12-31 17:00 m4-1.4.18/ChangeLog-2014 > -rw-rw-r-- 0/0 63687 2016-12-31 16:34 m4-1.4.18/maint.mk > -rw-rw-r-- 0/03912 2016-12-31 17:37 m4-1.4.18/ChangeLog > -rw-rw-r-- 0/0 69156 2016-12-31 17:25 m4-1.4.18/aclocal.m4 > -rw-rw-r-- 0/02590 2016-12-29 15:32 m4-1.4.18/BACKLOG > drwxrwxr-x 0/0 0 2016-12-31 17:37 m4-1.4.18/tests/ > -rw-rw-r-- 0/03126 2016-12-31 08:54 m4-1.4.18/tests/getcwd-lgpl.c > -rw-rw-r-- 0/06134 2016-12-31 08:54 m4-1.4.18/tests/test-dup2.c > -rw-rw-r-- 0/04998 2016-12-31 08:54 > m4-1.4.18/tests/test-dup-safer.c > > Brendan. > > -- > > > On 26/08/2020 4:22 pm, Erik Botö wrote: > > Hi Brendan, > > Could you inspect the file in > /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz > to see if it is some kind of HTML file stating a download error? > > Check the file size, if it's small it's probably an error so open it > using an editor to see if you get any hints. Many corporate networks > will require the use of a proxy server, see e.g. > https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy for > hints on that. > > Cheers, > Erik > > On Wed, Aug 26, 2020 at 7:36 AM Brendan Simon (SEPL) > wrote: > > Hi, > > I'm new to Yocto and am trying to follow the quick start guide to get up and > running with poky. I'm using the latest Dunfel 3.1.2. > > I'm running Debian 10 Buster in a VirtualBox VM (guest), on a Windows 10 Pro > (host). > > I'm having trouble with the build fetching files and getting checksum > mismatch, however if I download the troublesome file with wget then the > checksum is correct. > > How do I fix this? > > Everything seems very complex with Yocto, but maybe that's because I'm new to > it. > > > $ time bitbake core-image-sato > Loading cache: 100% > |###| > Time: 0:00:01Loaded 1312 entries from dependency cache. > NOTE: Resolving any missing task queue dependencies > > Build Configuration: > BB_VERSION = "1.46.0" > BUILD_SYS= "x86_64-linux" > NATIVELSBSTRING = "universal" > TARGET_SYS = "x86_64-poky-linux" > MACHINE = "qemux86-64" > DISTRO = "poky" > DISTRO_VERSION = "3.1.2" > TUNE_FEATURES= "m64 core2" > TARGET_FPU = "" > meta > meta-poky > meta-yocto-bsp = > "my-yocto-3.1.2:569b1f5d67c57de957e243997c53ec2f81dc8dfe" > > Initialising tasks: 100% > |##| > Time: 0:00:09Checking sstate mirror object availability: 100% > |##| Time: 0:36:41Sstate > summary: Wanted 2547 Found 0 Missed 2547 Current 228 (0% match, 8% complete) > NOTE: Executing Tasks > WARNING: m4-native-1.4.18-r0 do_fetch: Checksum mismatch for local file > /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz > Cleaning and trying again. > WARNING: m4-native-1.4.18-r0 do_fetch: Renaming > /home/brendan/SEPL/Projects/Erntec/PMU/yocto_trial/poky/build/downloads/m4-1.4.18.tar.gz > to >
Re: [yocto] Yocto host not found
https://twitter.com/TheYoctoJester/status/1290569609100308480 Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs : > > I am seeing the following error: > > Gateway Timeout > > Server error - server 198.145.29.63 is unreachable at this moment. > > Please retry the request or contact your administrator. > > > Kindly help. > > > Regards, > > > Ripu > > > On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs wrote: >> >> Hi, >> >> It seems like Yocto is down again. >> >> http://downloads.yoctoproject.org/ >> >> Could you please help solve this? >> >> Regards, >> >> Ripu >> >> On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs wrote: >>> >>> It is working now. >>> >>> Thank you >>> >>> Regards, >>> >>> Ripu >>> >>> On Thu., Jan. 9, 2020, 4:44 p.m. Michael Halstead, >>> wrote: There was a brief outage while rebooting a storage device. The error should have been resolved several minutes ago. If you are still seeing this error please let me know. Michael Halstead On Thu, Jan 9, 2020 at 1:38 PM FLoraVLogs wrote: > > Also, I do see: > > Connecting to downloads.yoctoproject.org > (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection > refused. > > > On Thu, Jan 9, 2020 at 3:37 PM FLoraVLogs wrote: >> >> Hi, >> >> I tried to go into the following: >> http://downloads.yoctoproject.org/ >> >> I get the following error: >> >> >> Host Not Found >> >> DNS error (the host name of the page you are looking for does not exist) >> or Server did not accept the connection. >> >> Please check that the host name has been spelled correctly. >> >> Regards, >> >> Ripu > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50191): https://lists.yoctoproject.org/g/yocto/message/50191 Mute This Topic: https://lists.yoctoproject.org/mt/69588660/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Remove connman package from yocto sdk.
Howdy! Am Di., 28. Juli 2020 um 07:19 Uhr schrieb NIKHIL PATIL : > > hi, > Still we ar facing same issue , > If anyone know, please help. > > On Fri, Jul 24, 2020 at 6:14 PM NIKHIL PATIL wrote: >> >> Hi team, >> We want to use NetworkManager to access internet using LTE module >> . but connman and Networkmaanger both are installed. >> >> I struggled so much to remove connman, I tried as follows :- >>1) Added IMAGE_INSTALL_remove = "connman" in local.conf >> but it still come with sato image. >> >> 2) Added DISTRO_FEATURE_remove = "connman" in local.conf >> but it still come with sato image. >> >> By default connman is coming in image , how to remove connman ? Do not remove connman. If you don't need it, then do not even build and install it. find out what pulls it in, and change that. Additionally, tinkering with that through local.conf is a bad practise: create your own image recipe and start from there. Greetz -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50110): https://lists.yoctoproject.org/g/yocto/message/50110 Mute This Topic: https://lists.yoctoproject.org/mt/75765466/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] #toolchain #yocto #devtool #linux
Howdy! Am Di., 28. Juli 2020 um 07:09 Uhr schrieb : > > Hi, > I am trying to build a yocto demo-coreip-cli image for my custom RISC-V SOC > which only supports imafd instructions. For the compilation of cross > toolchain that is used by Bitbake, I tried changing cross-binutils.inc recipe > and cross-gcc.inc recipe in openembedded-core layer by including > “–with-arch=rv64imafd” in "EXTRA_OECONF " variable. Is there anything else I > am missing or doing wrong? Thank You. Patching the cross toolchain should be the last resort. First, you should create a MACHINE definition that suits your needs and adjust the tune flags there. Greetz -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50109): https://lists.yoctoproject.org/g/yocto/message/50109 Mute This Topic: https://lists.yoctoproject.org/mt/75838691/21656 Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto Mute #toolchain: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/toolchain Mute #linux: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/linux Mute #devtool: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/devtool Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Building of warrior branch fails when building with Ubuntu 20.04 LTS #qemu #yocto #linux
Howdy! Am Di., 21. Juli 2020 um 09:07 Uhr schrieb Bernd : > > Hello, > > we are using the warrior branch for our embedded Linux project. Since Ubuntu > 20.04 LTS has been released we would like to switch from 18.04 to 20.04. > However, Ubuntu 20.04 now uses glibc-2.31 where the stime function has been > replaced. Therefore the build process of qmu-native-3.1.1.1 fails with the > following error code: > > /opt/ti/tq-yocto/build/tmp/hosttools/ld.bfd: linux-user/syscall.o: in > function `do_syscall1': | > /opt/ti/tq-yocto/build/tmp/work/x86_64-linux/qemu-native/3.1.1.1-r0/qemu-3.1.1.1/linux-user/syscall.c:7404: > undefined reference to `stime' > > Is there a work around? The usual approach is to build inside a defined container, like pyrex or CROPS, for example. Greetz > > Thanks a lot for your help, > Bernd > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50032): https://lists.yoctoproject.org/g/yocto/message/50032 Mute This Topic: https://lists.yoctoproject.org/mt/75699199/21656 Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto Mute #linux: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/linux Mute #qemu: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/qemu Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] How to completely uninstall a pre-installed package in Yocto #linux #yocto
Howdy! Am Mi., 15. Juli 2020 um 07:40 Uhr schrieb Soi, Sheng Leong : > > The question is how to completely uninstall the pre-installed package in > Yocto. Thanks > > I found out that one of the packages in Yocto is unwanted, and wish to > completely uninstall the package. > In contrast to a general purpose distribution where you have little control over the default set, there is no need to install anything you do not want. So the correct solution is: do not install that package. Even moreso, removing it later might be impossible if the image doesn't have package management enabled. Greetz -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49958): https://lists.yoctoproject.org/g/yocto/message/49958 Mute This Topic: https://lists.yoctoproject.org/mt/75515307/21656 Mute #yocto: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/yocto Mute #linux: https://lists.yoctoproject.org/g/yocto+yocto/mutehashtag/linux Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] how does "bitbake meta-toolchain" map to a particular "image" when generating SDK?
Howdy! Robert P. J. Day schrieb am So., 5. Juli 2020, 23:27: > > Quoting Richard Purdie : > > > On Sun, 2020-07-05 at 15:24 -0400, Robert P. J. Day wrote: > >> Quoting Ross Burton : > >> > >> > On Sun, 5 Jul 2020 at 11:50, Robert P. J. Day > >> wrote: > >> > >however, one can also generate a standard SDK with the generic > >> > > (image-independent): > >> > > > >> > >$ bitbake meta-toolchain > >> > > > >> > > which clearly does not identify an image (all that recipe does, > >> > > really, is "inherit populate_sdk"), so i *guessed* that using that > >> > > command will generate a standard SDK based only on what can be found > >> > > in the various .conf files and associated variables (MACHINE, > DISTRO, > >> > > etc.) without being tied to a particular image. > >> > > > >> > >just about to dive into the details, but is the above at least a > >> > > simplistic way of looking at it? > >> > > >> > At the most fundamental level, you've asked bitbake to build > >> > 'meta-toolchain'. Looking in meta-toolchain.bb will show you what > >> > that entails. It's basically just the compilers and a few other tools > >> > that were added as needed over the years. > >> > >>i'd assumed as much, but is there a reason that the meta-toolchain > target > >> is not mentioned at all in the SDK manual? Would that not be the right > >> place to mention it, even briefly? > > > > meta-toolchain is really old, from the days before the populate_sdk > > task for images existed. It was created as a compatibility artefact and > > as an example to show you could do standalone SDKs like that without > > images. > > > > I'd imagine its not mentioned as we envisaged the populate_sdk tasks > > taking over from meta-toolchain. I'm not even sure we test meta- > > toolchain on the autobuilder. It probably continues to work as its so > > similar to buildtools-tarball and friends. > > > > Should it be mentioned? Maybe... > >that actually clears things up. i'll let others higher up the food chain > decide if the meta-toolchain target should be documented, or if it's > entirely superseded by the populate_sdk tasks. > I actually can see more use cases coming up due to the increasing interest in building bare metal targets. My vote would be on documenting, and preferably also testing. Greetz > > rday > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49879): https://lists.yoctoproject.org/g/yocto/message/49879 Mute This Topic: https://lists.yoctoproject.org/mt/75311311/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
