**** BEGIN LOGGING AT Wed Jan 10 03:00:02 2018 Jan 10 04:58:53 I'm adding libSDL2-ttf package but yocto complains it cannot be compiles because of -lGL flag. How can I remove this flag and in which file? Jan 10 06:34:34 How can I build only the rootfs.gz instead of sdcard.gz? Jan 10 09:06:27 yocto poky master is failing to build core-image-minimal due to ERROR: glibc-locale-2.26-r0 do_package: QA Issue: glibc-locale: Files/directories were installed but not shipped in any package: /usr/share/i18n ... Jan 10 09:30:48 New news from stackoverflow: How to add package "iw" into linux kernel generated by open-embedded Jan 10 09:31:23 mcfrisk: its possible some configuration broke, not sure its any of our standard ones though... Jan 10 09:36:49 learningc: IMAGE_FSTYPE += " tar.gz" Jan 10 09:39:24 RP: I have small modifications to default local.conf to test patches before sending upstream to you: INHERIT += "buildhistory cve-check" and DISTRO_FEATURES += "systemd". trying the workaround LOCALE_GENERATION_WITH_CROSS-LOCALEDEF_forcevariable = "0" from https://bugzilla.yoctoproject.org/show_bug.cgi?id=12265 Jan 10 09:39:24 Bug 12265: major, Medium+, 2.5 M2, ross.burton, NEW , Can't build older versions of glibc when host features version 2.26 Jan 10 09:40:50 mcfrisk: that looks like a totally different failure and one I thought we'd fixed Jan 10 09:41:17 http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=pyro&id=a75a2f4272226e924d8c9deb699a19ca9e606a5b Jan 10 09:41:56 RP: indeed, workaround doesn't help and build fails with the same error. Jan 10 09:42:20 mcfrisk: I just closed that bug.... Jan 10 09:51:37 Hi, I am porting a u-boot-fw-utils recipe to Yocto 2.4, and I get the following error '/bin/sh: 1: cc: not found'. Any ideas how to fix that? Jan 10 09:51:51 I need to indicate in the recipe somehow that the native toolchain should be available, but not sure how to do that Jan 10 10:00:54 New news from stackoverflow: yocto questions about adding rsyslog Jan 10 10:02:09 ttllkk: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=21db71990bdaac6740873f591fc11b2e54caa217 ? Jan 10 10:38:55 RP: thanks! Jan 10 10:50:30 RP: DISTRO_FEATURES += "systemd" triggers the glibc-locale build failure with core-image-minamal. odd. Jan 10 11:17:21 hi, folks! Jan 10 11:21:16 has somebody an expirience to use prebuilded u-boot images with yocto (through bsp layers may be)? Jan 10 11:39:53 hello Jan 10 11:40:09 what happened with the gzipnative.bbclass in rocko? Jan 10 11:41:12 it's not there as far as i see Jan 10 11:42:23 cornel: see 39865fdf3698a130f792d41853f9c9ca1901e335 Jan 10 11:42:49 (first result in git log -G gzipnative) Jan 10 11:43:33 ah Jan 10 11:43:36 now isee Jan 10 11:43:41 thank you rburton Jan 10 11:59:43 I'm getting this error, " nothing provides packagegroup-core-boot needed by packagegroup-distro-base-1.0-r83.3.qemuarm" but is available.. anybody have idea? Jan 10 12:00:29 it gives me a solution "do not ask to install a package providing packagegroup-base-extended" what it means? Jan 10 12:01:19 New news from stackoverflow: add extra files to bitbake recipe Jan 10 12:06:09 rburton, and gummiboot was replaced by systemd-boot, right? Jan 10 12:41:52 cornel: yes Jan 10 12:43:06 has somebody an expririence with u-boot? Jan 10 12:58:27 acrap: ask your question Jan 10 13:02:39 i have a precompiled u-boot and i need to use it with yocto. Is it possible? Where could i get information about? Jan 10 13:04:40 acrap: you can certainly write a recipe that takes a pre-build binary, instead of compiling a binary from source Jan 10 13:05:06 acrap: it's better to compile though Jan 10 13:06:49 kanavin: i see... Do you have some links with examples how to do that? Jan 10 13:07:57 acrap: how to do what? Jan 10 13:08:46 first one for example Jan 10 13:09:11 acrap: not particularly right now Jan 10 13:09:57 ok. if you will, just remember about me :) Jan 10 13:10:33 acrap: look at recipes in oe-core that use local files in SRC_URI, dwarfsrcfiles for instance Jan 10 13:10:43 acrap: saying wat do you want to get would be helpful Jan 10 13:11:17 mckoan: it is a just a luck in language skills, sorry. Jan 10 13:11:29 *lack Jan 10 13:13:51 Is there a good way to rearrange this? I want IMAGE_NAME set from VSI_IMAGE if VSI_IMAGE is set. Otherwise VSI_IMAGE shall be the default IMAGE_NAME. E.g. will circular references like VSI_IMAGE ?= "${IMAGE_NAME}"; IMAGE_NAME = "${VSI_IMAGE}" work? Jan 10 13:25:45 hi guys, any ideas how to debug wic issues (I'm tryint to integrate mender to orangepi, but when creating sdimg it fails with strange error, log can be found here: https://groups.google.com/a/lists.mender.io/d/msg/mender/KiUqvXIY7dA/-EoenniyEQAJ) Jan 10 13:30:12 thank you rburton Jan 10 13:30:45 open-nandra: Hi, can you show your .wks file? Jan 10 13:36:07 this seems to be harder: where has 'tremor' gone? is not present anymore in rocko Jan 10 13:36:21 git log -G tremor does not give any result Jan 10 13:36:31 grrrr Jan 10 13:36:36 i was in the wrong repo :( Jan 10 13:36:52 ]of course is there Jan 10 15:00:34 hello. If you split files installed in packages via PACKAGES and FILES vars. why build system puts everything to the libxxx1.ipk? The ipks I have set at PACKAGES are not created at all but packages-spilt folder is ok Jan 10 15:05:45 files is processed in the order of the PACKAGES. So if you have a wild card 'early', you can end up including all of the files there, and they won't be included in the later packages. The processing only picks the first match and puts it into that package Jan 10 15:07:27 fray: I agree with you. But then wouldn't be wrong the file placement in packages-split folders? Jan 10 15:08:03 packages-split will match the .ipk/.rpm/.deb Jan 10 15:10:36 fray: it does not. packages-split are correct. All files are in correct folders places. But yocto does not create all these ipks. Instead in log writes: Jan 10 15:11:37 fray: Packaged contents of las-occ into liblasif1.ipk Jan 10 15:11:49 change to another format and check what it's doing. Jan 10 15:11:59 might be a flaw in the .ipk packaging.. Jan 10 15:12:19 hmm I will do Jan 10 15:55:11 fray: I found what the problem is. If between the files I install there is also a library inside eg libxxx.so.1 then it creates the libxxx1.ipk and puts everything inside there and not in the package I state in PACKAGES and FILES Jan 10 16:16:33 longshot but does anyone have any clues on how to fix " has relocations in .text [textrel]" QA warnings for SH4 architecture. I'm getting them when trying to build openssh and it's causing segv. Compiler logs confirm -fPIE and -pie. Jan 10 16:26:23 is it possible to install the same shared lib to 2 different places and to 2 different packages? Jan 10 16:38:50 Tamis: 'cp' Jan 10 16:38:58 in do_install, cp it. Jan 10 16:39:08 god knows why you'd want to do that though Jan 10 16:46:58 Hmm, bugzilla.yoctoproject.org should update to newer TLS, had to override user.js from ghacks in my firefox profile to no longer require 1.2 :) Jan 10 16:48:52 is there a way to include a image into another? Mainly because I want to have it listed in the manifest. Now I install the inner image with a POSTPROCESS_COMMAND, but that bypasses the manifest listing Jan 10 16:54:15 @sveinse I use do_rootfs[depends] += "xxx-image:do_image_complete" in the containing image Jan 10 16:54:43 rburton: it does not work. ok the cp or install commands works fine. But the packaging not. You cannot have 2 different packages or I couldn't find a way to do that. Jan 10 16:55:14 martint: yes, getting it built and depended on is fine. But this does not get it included in the manifest. Jan 10 16:55:20 you're not going to be able to have multiple packages owning the same file Jan 10 16:55:32 Tamis: of course you can, you're saying "i want two separate files in different packages". Jan 10 16:57:31 rburton: the same shared lib to 2 different places and then to different packages Jan 10 16:57:50 s/the same shared lib/two different files/ Jan 10 16:58:11 clearly you can put files in packages Jan 10 16:58:19 basically, you're not driving FILES right. Jan 10 17:00:53 I wonder if the manifest generator can be tweaked to include an extra entry Jan 10 17:01:03 I want to have 2 images a and b. One will have package a and the other package b. those packages need to have the same so but in different places Jan 10 17:02:03 That what I trying to do. But the recipe does not create those 2 different packages. Instead it creates one libxxxx Jan 10 17:02:18 ...or if its easier to make an encapsulation recipe (or bbclass) which includes the inner image and outputs a normal packages which then can be installed with IMAGE_INSTALL Jan 10 17:03:25 Tamis: debian-renaming will rename the package to match the soname, so turn that off (or set PKG for each one) Jan 10 17:04:42 rburton: hhhmm that's new to me! ty I will try it Jan 10 17:07:50 Is there a convenient way to find if a particular file is included in an image BEFORE I run bitbake? Jan 10 17:16:10 Adam___: no, because bitbake doesn't know what files are built by a recipe until its been built Jan 10 17:16:32 (same way you can't ask a source rpm what files it contains) Jan 10 17:17:00 @rburton I see. There is no --dry-mode? Jan 10 17:17:11 --dry-run* Jan 10 17:17:18 Adam___: how would it be a dryrun if its building stuff to find out? Jan 10 17:17:36 Ah ok Jan 10 17:17:56 Ty Jan 10 17:18:30 trivial example is a recipe that creates a file with a random name in /usr/bin, and then packages /usr/bin/* Jan 10 17:18:34 rburton: Thanks a lot! That DEBIAN_NOAUTONAME variable made the trick Jan 10 17:18:54 I have wished for a package.yoctoproject.org with a database of a standard architecture, making it searchable to find the package or recipe or layer when you know what file you're looking for Jan 10 17:18:56 rburton: now the correct packets are created Jan 10 17:19:17 sveinse: what distro would that build for? Jan 10 17:19:41 rburton: poky, world. As a starting point at least. Jan 10 17:19:46 *could* do it for oe-core nodistro on x86 Jan 10 17:20:03 It wouldn't be perfect but 95% of most files don't move across distros and machines Jan 10 17:20:41 I do this all the time for packages.ubuntu.com for finding what package or source package provides what file Jan 10 17:20:55 sveinse: build debs and use the same tools they use? :) Jan 10 17:21:29 To remedy it, I have a world build of qemux86 poky just to collect the ipks and have an index of them so I can search them. Helped me a dozen times Jan 10 17:22:08 even though I don't build for x86 nor poky Jan 10 18:28:15 Hey I'm trying to add systemd to a YP2.2 build. After a brief search, I added this to my local.conf: Jan 10 18:28:23 DISTRO_FEATURES_append = " systemd" Jan 10 18:28:23 DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit" Jan 10 18:28:23 VIRTUAL-RUNTIME_init_manager = "systemd" Jan 10 18:28:23 VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" Jan 10 18:28:36 then re-baked. Jan 10 18:28:57 All seemed fine until do_rootfs which produced: Jan 10 18:29:14 * calculate_dependencies_for: Cannot satisfy the following dependencies for packagegroup-dey-network: Jan 10 18:29:15 * busybox-ntpd * Jan 10 18:29:15 * opkg_solver_install: Cannot install package packagegroup-dey-network. Jan 10 18:29:15 * calculate_dependencies_for: Cannot satisfy the following dependencies for packagegroup-base-extended: Jan 10 18:29:15 * busybox-hwclock * busybox-static-nodes * Jan 10 18:29:15 * opkg_solver_install: Cannot install package packagegroup-base-extended. Jan 10 18:29:17 * calculate_dependencies_for: Cannot satisfy the following dependencies for packagegroup-dey-bluetooth: Jan 10 18:29:21 * bluez5-init * Jan 10 18:29:23 * opkg_solver_install: Cannot install package packagegroup-dey-bluetooth. Jan 10 18:29:25 lipse-debug. Jan 10 18:30:01 Did a little more searching and found a suggestion to do a cleansstate, which I did but no help Jan 10 18:31:03 Anybody give me a clue where to go next? Jan 10 18:31:04 I've built yocto and managed to run it using `runqemu qemuarm`. Is there a standard procedure for taking the contents of `yocto/poky/build/tmp/deploy/images/qemuarm` and cooking up an SD card that I can boot on a real device? Jan 10 18:38:13 xthunderheartx: the problem you are having comes from the packagegroupo you are trying to use in your images, they depend on busybox alternatives which systemd image do not have, as a simple answer you can either modify the recipes to not depend on busybox and staisfy those dependencies with something else: e.g. instead of busybox-ntpd depend on openntp or ntimed or something, you have to do that for each of Jan 10 18:38:15 those Jan 10 18:40:27 spierepf: is not as simple as it sounds, a qemuarm image will not work on real hw as is, wic is the tool used to create images, although its really gonna depend on what hardware/board you have Jan 10 18:42:53 aehs29: Thanks. I've got the ADZS-SC589-EZLITE eval board. Jan 10 18:43:13 aehs29:Thanx for the pointer. I'll go look some more and see what I can noodle out. Jan 10 18:50:48 spierepf: Ideally you should create a BSP, you may want to take a look at the code used to create images for other ARM devices, such as the raspi or beaglebone or something, and base your work on that, but like I said, every device works differently Jan 10 18:52:06 spierepf: I believe meta-linaro has generic bsps for ARM devices, you may want to start there Jan 10 18:53:39 aehs29: Yes, I'm trying to create a BSP. I guess I'm trying to figure out what the steps are for creating one. http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html is pretty thin on details. :) Jan 10 18:54:01 aehs29: I'll look at meta-linaro. Thanks. Jan 10 19:25:21 Hey Alejandro, the thing is that core-image-minimal builds ok and even boots weirdly enough ... It's core-image-base that upchucks. Jan 10 19:44:07 rburton: FYI, I tried building again the default image on ext4 instead of ZFS, and it worked. So there's probably something with ZFS that yocto doesn't like. Jan 10 19:46:02 I'll give it another shot on ZFS, but on the krogoth or pyro branch. As I said, it builds at my workplace and we used those branches... maybe something broke since Jan 10 19:51:12 xthunderheartx: yes, you need to take a look at the difference between minimal and base recipes Jan 10 19:52:58 Aw-ite. Jan 10 19:53:13 xthunderheartx: also, I would try to build a systemd image without any layers at first, packagegroup-dey-network comes from digi-dey, I would get rid of that at first, ensure I can get an image and add stuff on top of it gradually Jan 10 19:56:08 Yeah Digi is doing our hardware based on the iMX6ul SOM. Trying to add systemd to the base they provided us. I'll back up a bit. Jan 10 19:57:58 Honestly I really almost need to do a custom image. We need a skinnier stack that boots faster. Jan 10 19:59:06 I'm the best resource we have for yocto and that is not saying much. Jan 10 20:03:17 sfrigon: thats very good to know. please try switching back to zfs and seeing if you can break it on demand Jan 10 20:03:38 sfrigon: if you can, the temp/log.whatever for the failing task on both zfs and ext would be *much* appreciated Jan 10 20:31:20 rburton: Where should I copy my temp/log, on pastebin? Because yes it breaks on demand, I am unable to build at all on my personnal machine (it is not a "glitch" that occur from time to time) Jan 10 20:36:30 hey Jan 10 20:37:54 I am trying for days to build poky with meta-xilinx for the zybo-board. Now i have everything on the rocko branch. Running bitbake core-image-full-cmdline gives me the following error: Jan 10 20:38:08 ERROR: Nothing PROVIDES 'virtual/bitstream' Jan 10 20:38:24 does someone have an idea whats wrong? Jan 10 21:05:22 xthunderheartx: thats alright, youll get there, ramping up takes a while but its worth it Jan 10 21:19:24 symm4try looks to me that its something specific to meta-xilinx, perhaps you are in the wrong branch?, and got a git grep to see what should provide bistream from meta-xilinx Jan 10 21:19:34 symm4try: ^^ Jan 10 21:32:23 aehs29: thanks! Jan 10 22:10:35 anyone using the digilent zybo here? Jan 11 00:02:37 sfrigon: pastebin is fine, or email ross.burton@intel.com Jan 11 00:57:53 How do I get yocto to produce rootfs.tar.bz2? Jan 11 01:16:17 learningc: look at IMAGE_FSTYPE Jan 11 01:21:51 aehs29, I added IMAGE_FSTYPE += " tar.bz2" in my local.conf but has not produced the image in my deploy/image/board folder. Any idea why? Jan 11 01:59:29 learningc: its actually IMAGE_FSTYPES, theres a typo on it Jan 11 02:03:33 aehs29, Thanks. works now :) **** ENDING LOGGING AT Thu Jan 11 03:00:01 2018