**** BEGIN LOGGING AT Tue Dec 19 03:00:01 2017 Dec 19 07:25:23 anyone there? Dec 19 07:26:55 Hi guys. I got a really weird error at the end of a yocto build. (Rocko). Dec 19 07:26:56 Error Summary Dec 19 07:26:56 ------------- Dec 19 07:26:56 Disk Requirements: Dec 19 07:26:56 At least 275MB more space needed on the / filesystem. Dec 19 07:26:56 DEBUG: Python function do_rootfs finished Dec 19 07:27:05 failed Dec 19 07:27:28 there's enough space on the filesystem, so I don't know how to tackle it. any ideas ? Dec 19 07:29:27 rfried: try defining IMAGE_ROOTFS_SIZE=xxx Dec 19 07:34:44 how can I append/override an operation of "do_unpack" task Dec 19 08:11:17 xtron: do_unpack_append ? Dec 19 08:19:34 nayfe: actually I can't uncompress a "xx.tar.gz" with error "not a gzip format", I want to replace/override this operation... Dec 19 08:20:17 anybody knows if the determinism patch from Richard Purdie "providers: fix determinism issue" ebce92bf fixes the patches apply order issue? Dec 19 08:23:14 xtron: file is corrupted ? Dec 19 08:24:10 nayfe: no, I don't think so, I downloaded the file from browser, same size Dec 19 08:25:16 xtron: but what are you going to do with the file if you can't uncompress it? Dec 19 08:26:40 kanavin: I can uncompress it with different command "tar xvf file_name.tar.gz" Dec 19 08:28:05 kanavin: I think this can be an alternative solution, recipe is using oe_make which perform all the operation automatically Dec 19 08:28:39 https://lists.yoctoproject.org/pipermail/yocto/2011-November/003628.html Dec 19 08:29:28 by the way, the above commit is in 'bitbake' Dec 19 08:30:04 xtron: then it's a plain tar file and you should rename it Dec 19 09:24:07 cornel: I doubt it changes patch application order Dec 19 09:49:46 RP, thank you Dec 19 10:15:48 I am doomed to never being able to understand how Yocto is configured Dec 19 10:16:28 I have a project which is supposed to place a test app in an image at a certain path, but it's not showing up in the image at all, let alone at the path specified Dec 19 10:17:02 I have no idea why Dec 19 10:17:31 I can see that the test app is specified in an .inc file, and it's being built correctly Dec 19 10:18:28 So, how do I understand why it's not being included in the image Dec 19 10:19:12 Smit-Tay: work through the chain of events. Is the package containing this app correctly generated? Do you include that package in your image? Dec 19 10:20:10 How do I know if the package is being generated ? How do I know what it's called ? Dec 19 10:21:40 Smit-Tay: your test app has a recipe? Dec 19 10:22:02 Smit-Tay: look in the workdir of that recipe (where its being built) and see if a package is generated there? Dec 19 10:22:20 I guess it does, yes, it's called "test-logging" Dec 19 10:23:46 once you've built it, using oe-pkgdata-util is a good way to verify what got packaged Dec 19 10:24:43 $ oe-pkgdata-util list-pkg-files -p test-logging Dec 19 10:25:09 then you need to remember that simply building a recipe doesn't put it in you image, because you could be building more than one image Dec 19 10:27:19 *mahlzeitbussi* Dec 19 10:27:27 meh, ETERM Dec 19 10:27:28 The recipe is specified to be included in the image I've built Dec 19 10:28:41 rburton: your wish is my command http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/commit/?h=devel&id=578e67a2c752b84ae52e7b46e05e961dc38220f3 Dec 19 10:29:04 woo Dec 19 10:29:51 It seems like the only tool I have to understand anything with yocto is grep. And then I get lost is a ridiculously convoluted series of variables which in fact I can't know, because part of the variable name is itself a variable. Dec 19 10:30:36 Smit-Tay: have you checked that the package contains the file you expect with oe-pkgdata-util? Dec 19 10:31:23 The command you specified makes it look like the packages that match don't contain the file I am interested Dec 19 10:32:05 What is the difference between IMAGE_FEATURES and IMAGES_INSTALL ? Are they both for installing packages? Dec 19 10:32:08 Smit-Tay: that makes it sound like the package isn't being correctly generated then (so it is likely in the image but doesn't contain what you expect) Dec 19 10:32:26 learningc: features are groups of packages Dec 19 10:32:43 Ahhhh! Dec 19 10:32:43 OK, so how do I figure out why that would be ? Dec 19 10:33:26 RP, Are those groups of packages defined of single packages somewhere? Dec 19 10:33:58 Smit-Tay: have another look at your recipe and work out why its not doing what you expect. pastebin it if you can. Dec 19 10:34:32 The problem I have is that I am worried about leaking proprietary information Dec 19 10:37:17 https://pastebin.com/7x859pVZ Dec 19 10:37:34 sanitized, to ensure confusion (mine) Dec 19 10:38:38 Where can I find a description of what a package contains? Dec 19 10:41:34 learningc> oe-pkgdata-util list-pkg-files -p ? or in target if you have packagemgnt, something like rpm -ql ? Dec 19 10:43:21 So, that line is in a file, which is then "required" by a .bb file which is in a recipe directory Dec 19 10:44:58 That recipe is specified in several other layers Dec 19 10:45:25 and ultimately those layers are incldued in the image Dec 19 10:46:53 I don't understand why that recipe is mentioned so frequently, it's specified in about 20 other .bb files Dec 19 10:48:38 Smit-Tay: that really doesn't help, but if the intention is that the line pulls in the package, then it should be using the package name, not the file inside the package Dec 19 10:49:15 recipes create packages which contain files. images use IMAGE_INSTALL etc to list the *packages* they install. Dec 19 10:49:22 (this is in the docs) Dec 19 10:49:27 hello, I wish to check ipk package dependencies and install opkg packages without using the opkg CLI tool, but directly from my Qt application. Is it a good idea to integrate libopkg directly into the application? Dec 19 10:50:01 eduardas_m: the api is unstable and may/will change but sure, as you can see from the source code opkg.c is very minimal Dec 19 10:50:54 Smit-Tay: if you are working with a layer that somone created before you, you need to ask questions about that layer from them Dec 19 10:51:35 Smit-Tay: when we can't see the layer contents, it's really difficult to help Dec 19 10:52:10 Smit-Tay: you're also having a problem with terminology. layers contain recipes that *can* be built. simply being in a layer doesn't do anything else. an image recipe says what packages it wants, and bitbake then finds recipes that build those packages. Dec 19 10:52:19 rburton: the thing that I find weird with the Yocto-generated SDK is that it ships the /usr/lib/pkgconfig/libopkg.pc for pkg-config in sysroot, but there is no /usr/include/libopkg directory with the headers for libopkg Dec 19 10:53:21 even though there is a Cflags: -I${includedir}/libopkg entry in libopkg.pc Dec 19 10:53:34 eduardas_m: yeah that was a bug in opkg, fixed in master Dec 19 10:53:43 you need to tell opkg to install the headers if you want them Dec 19 10:54:02 rburton: not in Rocko? I am using Pyro currently Dec 19 10:54:12 I understand. My problem is that within this build environment, absolutely any file (.bb, .bbappend, whatever) can add to IMAGE_INSTALL, and it can add via a variable whose name I can't even know because it's interpreted Dec 19 10:54:25 rburton: how do I tell it to install the headers? Dec 19 10:54:49 eduardas_m: see opkg's configure.ac Dec 19 10:57:46 rburton: thank you a lot for the information... but I guess now I have to learn autotools... Dec 19 10:57:58 Smit-Tay: IMAGE_INSTALL has effect only when used in local.conf or in an image recipe that you are building Dec 19 11:01:22 learningc: have a look at the top of meta/classes/core-image.bbclass which defines some IMAGE_FEATURES Dec 19 11:05:44 RP, Ok Dec 19 11:11:20 eduardas_m: just read it until you find the big comment telling you want to do if you want the API installed Dec 19 11:12:42 RP: aha had | Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "bzImage-4.12.16-yocto-standard" with the bonus debugging present Dec 19 11:14:59 rburton: cool, does it help? Dec 19 11:15:42 rburton: thank you... now I'm wondering how relevant the libopkg API deprecation comment actually is... libopkg ships with external solver enabled in poky by default? Dec 19 11:15:52 yeah Dec 19 11:16:51 it says The current libopkg API is deprecated so only build it if requested Dec 19 11:55:58 Is there a way to show the hierarchy of an image - IOW, how an image include a class which includes a package which includes a file ? Dec 19 12:26:08 Simt-Tay: bitbake -u taskexp -g ? Dec 19 12:53:13 $ bitbake -u taskexp -g had-image-dev Dec 19 12:53:14 FATAL: Unable to import extension module "taskexp" from bb.ui. Valid extension modules: depexp, goggle, hob, knotty, ncurses or puccho Dec 19 13:02:22 Smit-Tay: what yocto release are you using? taskexp is available only since Pyro (2.3) if I remember correctly Dec 19 13:02:55 that is when depexp got deprecated Dec 19 13:08:30 so, if I replace taskexp I get this: Please set DISPLAY variable before running this command DISPLAY is set. can't this dump to console ? Dec 19 13:09:19 Smit-Tay: no, both depexp and taskexp are GUI tools Dec 19 13:09:54 I had similar issues on Kubuntu 16.04 with taskexp Dec 19 13:11:13 GAWD !!! OK, rant omitted Dec 19 13:11:56 when will *they* learn ? Dec 19 13:17:16 What is argp DISTRO_FEATURE? Dec 19 13:41:11 Smit-Tay: well, run bitbake -g and it will dump to task-depends.dot Dec 19 13:41:26 Smit-Tay: next you'll complain that file is hard to read and you need a GUI ;-) Dec 19 13:50:44 sagner: in current oe-core it's not used, so i'm guessing it was to tweak eglibc back in the days Dec 19 14:11:23 rburton: hm I see.. So a distro should add it these days in case it gets reused somwhere? Dec 19 14:12:09 sagner: if you were making a new distro i'd double-check with a grep that its not being used, and just drop it Dec 19 14:48:37 when it's a .bbclass, is it a package I can install with IMAGE_INSTALL ? Dec 19 14:50:14 no Dec 19 14:50:25 a class provides common tasks/functionality/etc Dec 19 14:50:57 so the autotools class lets a recipe that uses autoconf/automake just do "inherit autotools" and it handles configure/compile/install Dec 19 14:51:04 ditto for the cmake class, etc etc Dec 19 14:51:16 the patch class is what provides the do_patch task Dec 19 14:56:47 I see Dec 19 14:57:09 What package does a .bb depends on? Dec 19 14:59:47 learningc> what do you mean ? Dec 19 15:01:12 I'm trying to install a package manually from source on target board, and I am trying to find out from .bb which package the package.bb depends on Dec 19 15:01:41 RDEPENDS in the package will list explicit dependencies, and any library dependencies will be added automatically Dec 19 15:04:22 Cannot see RDEPENDS but see DEPENDS, is it equivalent? Dec 19 15:05:54 no Dec 19 15:06:03 i suggest you read the documentation Dec 19 15:08:36 ok Dec 19 15:08:55 What's the difference between a meta-toolchain and a native toolchain? Dec 19 15:10:59 meta-* are layers and toolchain is a toolchain O.o meta-toolchain will probably provide a toolchain in yocto environment Dec 19 15:13:21 meta-toolchain is the recipe which builds our older sdk standalone toolchain for use outside the buildsystem as an SDK Dec 19 15:26:44 rburton: I probably have patches ready for testing, are we ready for another batch of changes on the AB? Dec 19 15:27:10 zeddii: sorry to keep mentioning it but I really need this defconfig change. I can add in a temp .cfg if needed? Dec 19 15:35:20 RP: just fired two runs, but another is welcome ;) Dec 19 15:35:36 rburton: did any have my patches in? Dec 19 15:35:57 RP: idiotically forgot to rebase the right branch to next Dec 19 15:36:47 rburton: ok. I guess I could use the other builder Dec 19 15:42:45 zeddii_home: ^^^ Dec 19 15:46:54 New news from stackoverflow: How to initialize Bluetooth in a startup script with Yocto Poky Linux Dec 19 16:16:42 I have this image (wic-based) image recipe https://bpaste.net/show/cf7237d93fd8, which fails in rocko with https://bpaste.net/show/af6a4446e088. Any ideas on why and how I can fix it? Dec 19 16:18:03 let's say my GUI application is running as a restricted user, but using opkg to install an update package should require root privilages... what is the appropriate way of handling this in an embedded system? Dec 19 16:18:50 eduardas_m: we use sudo for this. pinpointed to specific users and executables Dec 19 16:19:44 sveinse, thank you... do you know if this will work fine with Qt's QProcess? Dec 19 16:21:33 eduardas_m: I don't see why it shouldn't. Though, it complicates if you want interactivity, e.g. ask the user for the password or similar. We've setup with no password on certain operations. Dec 19 16:22:11 ...which essentially implies that the user has carte blanche root access for that function Dec 19 16:24:54 sveinse, I was kinda thinking about running a one-shot systemd service for running opkg and using the GUI to start that unit via d-bus... not sure if anyone uses systemd for installing packages on embedded systems though Dec 19 16:29:16 sveinse, also, because I am not deeply familiar with sudo specifics, I am not sure how one can actually specify both a user and a command for allowing some action without a password at the same time Dec 19 16:31:20 sveinse, I am not sure what the words "We've setup with no password on certain operations" means in practical terms for me.. i.e. how do I implement similar behaviour? Dec 19 16:32:11 eduardas_m: see the man page for the sudoers file Dec 19 16:33:34 kergoth, thank you Dec 19 17:31:28 Hi, one of the things I have not figured out in yocto is how to add a new utility to used by another .bb file later in the compilation. For example, I have a package that creates a utility called "mkimage". It needs to be used later in the kernel build recipe. The package nand-boot-redirect worked in morty but not in rocko. Dec 19 17:32:25 jpeters: you probably forgot to add it to the DEPENDS Dec 19 17:32:55 as rocko has recipe-specific-sysroots, so whereas previously you could just do bitbake foo and it stays in the sysroot forever, with rocko you get what the DEPENDS says Dec 19 17:33:00 (this is in the release notes, obviously) Dec 19 17:33:42 So if I add the nand_boot_redirect to the DEPENDS in the kernel recipe then Yocto ensure subcomponents are available? Dec 19 17:34:05 Thanks, trying that now. Dec 19 17:35:12 if you've done it idiomatically, nand-boot-redirect-native, but whatever Dec 19 18:21:29 The DEPENDS already includes nand-boot-redirect-native. The error I get during the build is "/work/jpeters/yocto/rw_rocko2/yocto_sc/rw20exp-wayland/tmp/work/rw20-rw20-linux-gnueabi/linux-rw20-system/4.14.1-1.0+gitAUTOINC+05f6615998-r0/recipe-sysroot/usr/bin/mkimage". It is trying to run it from the kernel build. Dec 19 18:23:48 The only place it is is getting installed is in nand_boot_redirect's own recipe-sysroot-native/usr/bin directory. I would expect it to be installed somewhere in a cross package directory where the kernel build could get to it and use it. Dec 19 18:26:55 I am sure I am missing a piece of Yocto understanding about how this kind if is populated to the correct place. The original code in the .bb file for nand_boot_redirect uses "addtask deploy before do_package after do_install" and the do_deploy directory does "cp mkiamge ${STAGING_DIR_NATIVE}/usr/bin" Dec 19 18:27:40 It looks to be like the recipe-sysroot directory is not getting pushed out but I don't know the correct way to get Yocto to do this. Dec 19 19:33:38 jpeters: sounds like the recipe is broken and not using $D correctly Dec 19 19:33:43 jpeters: pastebin it if you can Dec 19 19:37:58 * zeddii_home thinks he missed something Dec 19 19:48:53 anyone seeing a fetcher failure on psmisc? "ERROR: psmisc-23.0-r0 do_fetch: Fetcher failure..." -- I haven't used this machine in a while, so the downloads cache is somewhat stale.... Dec 19 19:53:46 not the fetcher's fault. "gitlab.com" doesn't even answer pings. :-( Dec 19 19:54:10 guessing there are no mirrors in the bb either. Dec 19 22:42:30 hi all! I'm trying to create my first overlay, which would modify some recipes from other one. I need to remove some features from the upstream-layer's list in a particular recipe Dec 19 22:43:38 how do variables expand? before or after the layers are flattened? Dec 19 22:44:03 e.g. in upstream repo I have: Dec 19 22:44:28 IMAGE_INSTALL += " \ Dec 19 22:44:30 [...] Dec 19 22:44:31 ${WIFI_SUPPORT} \ Dec 19 22:44:33 " Dec 19 22:45:03 I need to remove the whole wifi-related-stuff in my bbappend Dec 19 22:47:32 is it sufficient to remove just a ${WIFI_SUPPORT} from IMAGE_INSTALL (if so, how exactly?), or do I need to compose my own list of packages (excluding wifi-stuff) separately, overwriting upstream's IMAGE_INSTALL var? Dec 19 22:51:01 see the bitbake user manual Dec 19 22:51:07 your bbappend can set WIFI_SUPPORT="" Dec 19 22:51:31 then tell upstream that they should respect the wifi DISTRO_FEATURE Dec 19 22:52:07 ok, thanks for the tips! Dec 20 01:28:25 How do I find out what package install libdirect ? **** ENDING LOGGING AT Wed Dec 20 03:00:02 2017