**** BEGIN LOGGING AT Wed Aug 07 03:02:32 2019 Aug 07 08:50:29 Hello, I had this library in my recipe that was not installing dynamic libraries properly in my image. Now I found that the default prefix installation for it was "/opt/etherlab". I can override its prefix by giving it --prefix=/usr as a configuration parameter without a problem in my host computer. Aug 07 08:50:59 I believe I need to supply this parameter to EXTRA_OECONF += in my recipes .bb file Aug 07 08:51:25 How can I point the "right" /usr direction in my image? Thanks. Aug 07 09:01:59 I tried something like EXTRA_OECONF += "--prefix=${D}${prefix}" but I don't think it worked. I found the "D" and "prefix" from http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf here. Aug 07 09:02:12 fdav: that does probably help: http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf Aug 07 09:03:48 fdav: i think the prefix should be injected automatically. better check bitbake -e and the corresponding logs what the configure stage really receives Aug 07 09:06:14 fdav: have you implemented the do_install() in your recipe? I don't think that you have to EXTRA_OECONF anything. Aug 07 09:09:33 if you manually override do_install, then any target prefix you pass is ignored anyways as you're, well, manually overriding. Aug 07 09:19:35 I haven't, I use inherit autotools directly Aug 07 09:20:06 thats good, yes. Aug 07 09:20:11 I simply assumed that the thing I put into EXTRA_OECONF goes directly into "./configure" process of autotools Aug 07 09:20:31 fdav: thats the way its meant to be, yes. Aug 07 09:20:45 but it never hurts to check bitbake -e and the do_configure logs Aug 07 09:23:39 I have never used bitbake -e earlier, what to check for exactly or how should I use it? Aug 07 09:24:58 fdav: generally, its "bitbake -e $YOURRECIPE | less" or something comparable, because the output is extensive. then, search for EXTRA_OECONF to see if it actually carries what you expect Aug 07 09:33:02 fdav: or bitbake -e $YOURRECIPE | grep ^EXTRA_OECONF Aug 07 09:33:12 will give you directly line you're looking for Aug 07 10:57:53 opennandra: Thanks! Aug 07 10:58:24 LetoThe2nd: What I get is EXTRA_OECONF=" --prefix=/home/USER/workspace/ccimx6sbc/tmp/work/cortexa9hf-neon-dey-linux-gnueabi/ethercat-igh/0.1-r0/image/usr" Aug 07 10:58:27 it seems right Aug 07 13:08:23 why is DISTRO set by my default local.conf? And why does DISTRO ?= "foo" in my local.conf override DISTRO = "bar" in the image recipe? Aug 07 13:10:36 jmiehe: recipe data is local, conf data is global Aug 07 13:10:49 amen Aug 07 13:10:52 jmiehe: everything outside of the image recipe cannot see the setting. Aug 07 13:11:10 jmiehe: i have ALL my OE/YOP classes repeat that aloud. i advise you do so the same, maybe 3 times. Aug 07 13:11:18 :-) Aug 07 13:12:04 I've actually read that from you, already ;) Aug 07 13:12:36 So that sentence instantly cleared things up, thx^^ Aug 07 13:12:42 jmiehe: it begins to form a pattern, right? :) Aug 07 13:13:27 yup, cheers Aug 07 14:08:47 Hi, is there way to generate a packagegroup automatically? I'd like to generate a packagegroup of all build ptest and other tests in our platform (using custom bbclasses)? we would not use ptest image feature but instead use release images and install needed packages via the packagegroup before starting tests. Aug 07 14:38:29 complementary_globs() and COMPLEMENTARY_GLOB seems to be what I need, but I'd like to generate a packagegroup out of them instead of adding things to SDK or images.. Aug 07 15:59:34 RP: Is there a technical term for the phase where bitbake builds up the graph of tasks to be executed? Aug 07 16:00:17 JPEW: "runqueue preparation" ? Aug 07 17:55:11 RP: now that glibc 2.30 is in can you try out https://git.openembedded.org/openembedded-core-contrib/commit/?h=yoe/mut&id=50bfc2a16c214cea3a77cd4978008cd5a40ccbac Aug 07 17:55:37 I have added llvm-pipe to my local qemu builds as well and it seems to be working fine Aug 07 17:55:37 now Aug 07 18:43:31 khem: added Aug 07 19:13:44 RP:I also sent v2 for musl, which fixes the regression, which was genuine problem Aug 07 19:26:12 khem: great, it did look like a genuine failure Aug 07 19:26:29 khem: I've a test build running but will include that in the next run Aug 07 21:18:52 Yesterday I was asking questions about why I would be missing files in my sdk, I've figure it out Aug 07 21:19:26 Apparently, the do_populate_sdk function ignores all errors when installing "complementary" packages (*-dev *-dbg) Aug 07 21:19:49 It caches any exceptions, prints a warning and just continues on Aug 07 21:20:10 So none of the *-dev and *-dbg packages were getting installed Aug 07 22:06:39 JPEW: As an experiment we've setup the standard bitbake hashserv and https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/610 is a build against it on the autobuilder Aug 07 22:07:04 JPEW: looks like its not scaling, perhaps unsurprisingly Aug 07 22:24:54 RP, for that feature, you need to buy the commercial version ; ) Aug 07 22:26:59 armpit: you have one ready? :) Aug 07 22:27:32 nope, I am not that smart Aug 07 22:28:02 armpit: I happen to know JPEW does have a better server as it happens Aug 07 23:29:53 New news from stackoverflow: Failed to install a .deb package on a Yocto system using opkg Aug 08 02:20:27 * zeddii is back from the wilderness. Aug 08 02:20:45 if anyone messaged me here, I didn’t see it and my history only seems to be a day. **** ENDING LOGGING AT Thu Aug 08 02:59:57 2019