**** BEGIN LOGGING AT Thu May 02 02:59:57 2019 May 02 06:42:38 good morning May 02 08:24:42 Hi All. I'm having trouble getting static libs into my toolchain. I have a recipe that appears to generate the right contents within the *-staticdev* rpm, but these never make it into my toolchain when deployed, even though the image that defines the toolchain does include another recipe that DEPENDS upon the library. May 02 08:24:48 What am I missing?... May 02 08:30:22 JoeR: Yocto/OE builds libraries as shared by default, to enable a static add this into the library recipe DISABLE_STATIC = "" May 02 08:32:26 mckoan: Thank you! This IRC channel is a complete life line. Plus everyones so nice here. :-) May 02 08:33:15 JoeR: I'm actually inclined to take that as a personal insult. May 02 08:34:59 Noooo. You guys all do such a good job. I've had to maintain my own embedded distro entirely by hand before. Yocto is a massive project that saves me soooo much time. It *IS* a big project though, and I can't even keep up with the changes let alone all the documentation. May 02 08:35:16 JoeR: i was talking about the "nice". May 02 08:35:26 * LetoThe2nd is a grumpy sandworm! and proud of it! May 02 08:35:29 I'm entirely happy for someone to say RTFM if they can point at the appropriate section. May 02 08:35:50 Nah, you're all nice really. It;s a very friendly group, which isn't always the case I've found with some projects... May 02 08:36:11 JoeR: I'd expect you have to explicitly RDEPEND on the -staticdev package as well (but I don't really use static libs) May 02 08:36:13 now you got me depressed! May 02 08:36:55 jku: OK. I'll check that too. I don't like (or normally use) static libs, but that's all this very WIP project from a 3rd party is. So I'm left with what I'm left with. May 02 08:58:57 JoeR: As others have said, we disable building static libs by default so enabling them would be the place to start May 02 08:59:07 JoeR: on the most part they're old obsolete technology May 02 09:00:09 RP: The library I'm dealing with isn't really geared up for a "real install" as yet. So I suspect that's why I'm stuck with just archives. Weirdly they were built and installed into *-staticdev, just not installed into the toolchain, with no real effort on my part. May 02 09:12:28 JoeR: right, if they're built it will package them May 02 09:13:04 JoeR: you probably just need to explicitly this them as needed in the toolchain package dependencies May 02 09:13:41 RP: I thought I had by having the package as DEPENDS. So more specifically what do I need to do? May 02 09:14:21 JoeR: DEPENDS means its a build time dependency, it was built :) May 02 09:14:38 And yet it's not exactly a runtime dependency... May 02 09:15:38 RP: My toolchain is also my image. I'm not sure if that's the right way to do things? i.e. my image recipe also inherits populate_sdk. May 02 09:15:39 JoeR: TOOLCHAIN_TARGET_TASK_append = " foo-staticdev" ? May 02 09:15:57 OK. Will try that. Much appreciated. May 02 09:16:01 JoeR: images always inherit that by default May 02 09:16:05 Oh ok :-) May 02 09:54:21 How do I set the default target for systemd during the build? I didn't find anaything about that. May 02 10:25:03 So, coming back to the DEPENDS RDEPENDS thing with static libs (the toolchain as a whole I guess). DEPENDS are build time dependencies, and will be within the interim toolchain? RDEPENDS are run time so will be within the image itself. Is the static lib the weird one out that isn't either? May 02 10:25:58 JoeR: A static lib is a build time dependency, it's needed at, and only at, build time. May 02 10:27:52 So why are people suggesting that I need to RDEPEND on it? My issue is a static only lib not getting included in the deployed toolchain, despite being packaged and referenced as DEPEND from another packge. May 02 10:28:13 It's a pure static lib package. May 02 10:30:14 I'm trying to catch up on the previous discussion now by reading the history. Is the problem that the staticlib doesn't end up in the generated SDK built with "bitbake -c populate_sdk "? May 02 10:30:28 Yes. May 02 10:30:43 Didn't RP's suggestion work? May 02 10:31:10 Didn't seem to. Unless I put that in the wrong place. It's in the recipe for the package that needs the .a. May 02 10:31:25 No, it should go into the image recipe May 02 10:31:30 Ohhhhhhhhhhhhh. May 02 10:31:35 I'll try that then :-) May 02 10:31:38 Thanks you! May 02 10:31:47 Ahem. Thank you! May 02 10:34:11 on the same topic, is TOOLCHAIN_TARGET_TASK preferred to using the "staticdev" SDK image feature? May 02 10:34:26 I did the latter a couple of weeks ago (granted, with a lot more hoops to jump through...) May 02 10:34:27 JoeR: No worries, hopefully it will work now May 02 10:37:05 bjobjo: I guess the difference is if you want to just add just some -staticdev packages, or all. May 02 10:37:38 fair enough, I originally envisioned that just adding all of them would be easier May 02 10:37:44 Just so I'm learning here, what is the staticdev SDK image feature? May 02 10:37:44 it turned out not to be the case :) May 02 10:38:03 JoeR: DEPENDS just means that X needs to build before Y. There is no magic beyond that. If something dynamically links to X, we can detect that and add runtime dependencies automagically May 02 10:38:19 JoeR: https://www.yoctoproject.org/docs/2.6.1/ref-manual/ref-manual.html#ref-features-image May 02 10:38:20 JoeR: We have no way of knowing that you want this static lib only in the toolchain image May 02 10:38:38 bjobjo: Thanks. May 02 10:38:49 JoeR: hence you have to add an explicit directive to the image recipe to say to include it May 02 10:38:51 JoeR: also https://www.yoctoproject.org/docs/2.6.1/ref-manual/ref-manual.html#var-SDKIMAGE_FEATURES May 02 10:39:10 Righto. So it's a sort of weird middle ground I'm in, cos static libs aren't really "supported" but tolerated ;-) May 02 10:41:17 I'd say it's supported, but maybe not as easy to use as dynamic libs since it's not as easy to extract info about which libs are used. May 02 10:41:42 JoeR: we support them just fine, we just can't work with them as magically as we can with dynamic libs May 02 10:41:55 Understood. This is all new ground to me, first time I wanted to add something that was just a library rather than a bin into the image. May 02 10:42:05 Typical it's a weirdo lib. May 02 10:50:37 New news from stackoverflow: Error building qt5 for rspi : qt_build_config May 02 10:54:59 JoeR: you could also probably do something like SDKIMAGE_INSTALL_COMPLEMENTARY += "staticdev-pkgs" May 02 10:55:48 RP: OK. I'll look at that too. What does that variable represent? May 02 10:56:28 JoeR: sorry, I mean SDKIMAGE_FEATURES += "staticdev-pkgs" May 02 10:56:55 JoeR: that would cause the system to set SDKIMAGE_INSTALL_COMPLEMENTARY += '*-staticdev' May 02 10:57:06 which would mean the sdk would contain all *-staticdev packages May 02 10:57:15 (packages matching that glob) May 02 10:57:20 RP: OK. May 02 10:58:33 RP: OK. Would bloat the SDK, but would definitely get me there is what you're saying? May 02 11:01:14 JoeR: yes, giving you options May 02 11:02:21 RP: Appreciated. May 02 12:22:56 > nothing provides libdl.so.2 needed by icc-2016+1-r0.corei7_64 May 02 12:22:59 hmmmm what ? May 02 12:23:13 isnt libdl packaged with glibc ? May 02 13:45:47 aehs29, yes May 02 14:21:15 New news from stackoverflow: unable to execute do_install_append May 02 14:46:06 TOOLCHAIN_TARGET_TASK_append got me there. Thanks everyone for the help. May 02 16:23:38 hi, how to run the oeqa selftests? May 02 16:35:39 mcfrisk: "oe-selftest" ? May 02 16:35:58 mcfrisk: or possibly image tests with bitbake xxx-image -c testimage May 02 16:51:46 New news from stackoverflow: WLan0 connection on pi3 similar device[yocto] May 02 17:15:34 Hi, I'm using the `start-stop-daemon --start --background ...` to launch a daemon. In the daemon there a while/loop and inside the loop, there a call to establish an SSH tunnel. Once I call `start-stop-daemon --stop ...`, the process is killed, but not the child process of SSH tunnel connection. How can I kill it or unblock from it ? May 02 17:21:52 New news from stackoverflow: which utility produces "Poky (Yocto Project Reference Distro) 2.6.1 (none) /dev/console" **** BEGIN LOGGING AT Thu May 02 20:01:16 2019 May 02 21:31:46 I always seem to do the crazy things that trigger obscure bugs May 02 21:32:23 It's a skill at least I suppose **** ENDING LOGGING AT Fri May 03 02:59:57 2019