**** BEGIN LOGGING AT Mon Jan 22 03:00:02 2018 Jan 22 06:16:28 New news from stackoverflow: Issue with tool chain created using YOCTO fido branch Jan 22 06:46:34 New news from stackoverflow: how to clean the libs and headers files installed in yocto sysrootdir Jan 22 07:11:19 hello Jan 22 07:11:55 is sources.openmebedded.org still alive? i am unable to get boot from it Jan 22 07:12:07 boost Jan 22 07:25:44 Hi folks! I can't boot qemu with custom linux kernel (cause linux can't see vda devices). There is a boot log https://paste.gnome.org/puvsvltnu. Does anybody know what drivers i must enable in my custom defconfig to make it works? Jan 22 07:26:14 Now i've added this (VIRTIO_*) https://paste.gnome.org/pywvp505o Jan 22 07:27:14 also i tried to build this drivers as modules (m instead y) Jan 22 08:26:07 Where do I create my .bbappend? Jan 22 08:34:43 how can i configure yocto so othat, if one file was once found, it's stored locally and it does not have to look after it again? Jan 22 08:36:26 in the upstream, that is Jan 22 08:37:47 can this be achieved reusing the previous downloads/ directory and setting BB_NO_NETWORK in local.conf? Jan 22 09:47:11 New news from stackoverflow: Best way to config linux kernel depending on yocto image Jan 22 10:18:59 User__: see where original *.bb recept is placed. Yo gotta create the same folder in your layer and place bbappend there. Jan 22 10:47:21 New news from stackoverflow: Qt Overlay over GStreamer Jan 22 11:23:05 how can I add a compilation flag for an automake project in the Yocto recipe? Jan 22 11:23:07 Makefile.am:if BUILD_EXAMPLES Jan 22 11:23:21 I would like to define that 'BUILD_EXAMPLES' so that the the Makefile.am builds that Jan 22 11:39:48 ttllkk: you'll need to read autoconf to figure out how to set that Jan 22 11:40:02 the configure.ac will be setting BUILD_EXAMPLES Jan 22 12:06:37 rburton: I didn't know much about automake. that work, thanks! Jan 22 12:06:42 worked* Jan 22 13:09:04 Is there a way to list only direct dependencies in the output of 'bitbake -g '? Jan 22 13:09:38 what did I do wrong when I successfully built my application with all dependencies but the dependencies are not installed in the image? Jan 22 13:42:22 jaeckel: build depends != runtime depends, maybe? Jan 22 13:49:02 rburton: yeah it looks like, but I thought the runtime depends are automagically calculated!? Jan 22 13:51:57 jaeckel: if a binary links to a library, then the dependency for the library is added automatically yes Jan 22 13:52:21 so no dependency implies no linking Jan 22 13:56:34 uhm okay, because my binary links to several libraries but none of them was added to the image... I've add my binary via an RDEPENDS to the image, that's correct right? Jan 22 13:57:01 s/I've add/I've added Jan 22 14:04:45 jaeckel: if none of them were added but the binary really does link then you've found either a bug in the linking, or a bug in the library packaging Jan 22 14:05:02 if the libraries are in a non-standard place that might explain it Jan 22 14:10:43 rburton: they're all installed to /usr/lib and `readelf -d | grep NEEDED` shows them all Jan 22 14:11:33 I've added them now to the RDEPENDS in the packagegroup and they're installed now, but I thought that should be done automatically Jan 22 14:11:59 i presume the packagegroup isn't where the linking is happening right Jan 22 14:12:06 (as packagegroups have no content) Jan 22 14:12:38 read the pkgdata for the package containing the binary to verify the deps are missing (tmp/pkgdata/[machine]/runtime/[package] Jan 22 14:13:37 oh, oe-pkgdata-util can do that too Jan 22 14:13:43 oe-pkgdata-util read-value RDEPENDS [package name] Jan 22 14:14:08 uhm I don't have a pkgdata folder... sorry I'm still on krogoth... Jan 22 14:14:27 hello guys Jan 22 14:14:42 you do, but it moved Jan 22 14:14:44 now where was it Jan 22 14:14:49 in the sysroot maybe? Jan 22 14:15:29 yep Jan 22 14:15:32 is there any way i can bypass auxiliary vector?(http://articles.manugarg.com/aboutelfauxiliaryvectors ) Jan 22 14:15:58 and `oe-pkgdata-util read-value RDEPENDS ` returns empty-string Jan 22 14:16:10 jaeckel: well maybe that's the problem :) Jan 22 14:18:10 okay, so I've the dependencies in the recipe in the DEPENDS variable, what else should I do then? Jan 22 14:18:47 jaeckel: read log.do_package for that recipe and see if it says anything obvious Jan 22 14:19:03 I'm guessing #yocto chatter gets archived somewhere? I'm looking for a conversation I had last week. Jan 22 14:19:18 xthunderheartx: channel topic has a link Jan 22 14:19:23 thx Jan 22 14:20:08 My image is missing https support (wget https just hangs). I believe it's because gnutls-openssl is missing from the image. However, I seem unable to add it as DEPENDS to my recipe. I get Nothing PROVIDES 'gnutls-openssl', yet I see the package being built in deploy/ipks. How can I add this to my recipe or image? Jan 22 14:21:41 sveinse: 'just hangs' does not look like missing https support Jan 22 14:21:42 I have created a yocto recipe to add users and groups to image(this is all that is does) .In other packages I the actual ownership setting... but I can not use UIDs and GIDs Jan 22 14:22:02 john1987: did you use the useradd classes? Jan 22 14:22:09 yes Jan 22 14:22:48 kanavin: It might not be related to wget, since wget is a busybox app I see now. I tries using its --debug, but that is not supported in busybox. Anyways, the main problem is ssl not working in our application Jan 22 14:23:36 sveinse: in your app is your app's problem, surely. did you install ca-certificates? Jan 22 14:23:41 rburton: i inherited from useradd only in the recipe what adds the users and groups. In the rest of the recipies I added dependency on bb recipe that adds the users Jan 22 14:23:47 Comparing to our previous pyro build (this is on rocko), the manifest difference shows that gnutls-openssl is included on pyro Jan 22 14:23:57 rburton: I'll check Jan 22 14:24:39 rburton: look like I got it... the binary was missing +x ... m( ... thanks Jan 22 14:26:18 jaeckel: that would be it :) Jan 22 14:26:43 Hmm. ca-certificates is actually missing on both systems... Yet, SSL is working on pyro. Strange Jan 22 14:26:50 sveinse: that's just a (bad) compat library isn't it? Jan 22 14:27:28 rburton: yes probably, but I got something I can try. Thanks. Jan 22 14:30:58 rburton: do you advise on changing ownership in do_install or pkg_postinst ? Jan 22 14:31:22 installl Jan 22 15:05:27 ARRRRGGHHH! Apparently, bitbake exceeds my intellectual capacity. Jan 22 15:05:59 I get this error: configure.ac:110: error: possibly undefined macro: AC_MSG_RESULT Jan 22 15:06:17 when I fetch from a public git repo on gitlab Jan 22 15:06:51 but if I fetch from a subversion repo on sourceforge it goes away. Jan 22 15:07:13 same DEPENDS/RDEPENDS in both cases Jan 22 15:07:41 I know I must be telling it the wrong work dir or something. Jan 22 15:08:39 xthunderheartx: let me guess, the subversion repo has a generated configure file, the git repositority does not? Jan 22 15:08:52 (although if you use autotools.bbclass it should always run autoreconf) Jan 22 15:09:05 No. Both raw. Identical tree Jan 22 15:09:14 Same timestamps, too? Jan 22 15:10:05 Timestamps would be different as the original subversion hasn't been touched for years and I just forked it to gitlab right? Jan 22 15:11:08 I thought my working tree might be wonked up, but I cleaned it. Jan 22 15:12:30 Here are the relevant lines from the recipe: Jan 22 15:12:34 #SRC_URI = "git://gitlab.com/dposey/dbus-cxx.git;protocol=http" Jan 22 15:12:34 #SRCREV = "${AUTOREV}" Jan 22 15:12:34 #S = "${WORKDIR}/git" Jan 22 15:12:34 SRC_URI = "svn://svn.code.sf.net/p/dbus-cxx/code;module=trunk" Jan 22 15:12:34 SRCREV = "${AUTOREV}" Jan 22 15:12:35 S = "${WORKDIR}/trunk/dbus-cxx" Jan 22 15:12:37 DEPENDS = "dbus libsigc++-2.0" Jan 22 15:12:39 RDEPENDS_${PN} = "dbus" Jan 22 15:12:41 inherit autotools-brokensep Jan 22 15:13:30 The uncommented configuration works. Jan 22 15:13:57 Commented flops Jan 22 15:14:25 You probably need a pkg-config dependency, too Jan 22 15:14:47 See line 110 of the autoconf.ac: https://gitlab.com/dposey/dbus-cxx/blob/master/configure.ac#L110 Jan 22 15:15:01 PKG_CHECK_MODULES() is a macro provided by the autoconf files installed by pkgconfig Jan 22 15:16:24 Yeah I looked at it and it calls offending macro if the dependancy dbus fails, but it's there ... confuses the snot outta me. Jan 22 15:16:57 well, AC_MSG_RESULT is there, but PKG_CHECK_MODULES might not be unless you depend on pkgconfig Jan 22 15:17:48 K. So just add it DEPENDS and try again. Will do and thx 4 the help. Jan 22 15:28:42 Yep ... fixed it. Why??? Jan 22 15:30:41 xthunderheartx: because if you want to use pkgconfig macros in the configure.ac then you need to have pkgconfig installed Jan 22 15:31:06 xthunderheartx: "PKG_CHECK_MODULES() is a macro provided by the autoconf files installed by pkgconfig" Jan 22 15:31:16 either depend on pkgconfig-native, or inherit pkgconfig Jan 22 15:31:24 the latter just does the former, so i'd like to remove it one day... Jan 22 15:31:42 the warning you get when you don't have it available is obscure at best Jan 22 15:33:45 (thanks, autoconf) Jan 22 15:35:53 I am trying to transition a buildroot based system to a yocto/oe based one. Buildroot's busybox uses symlinks with relative paths (/sbin/getty -> ../bin/busybox) while yocto uses symlinks with absolute paths (/sbin/getty -> /bin/busybox.nosuid). Jan 22 15:36:33 Is there a configuration option to chage yocto's behaviour in this regard? Jan 22 15:37:10 * armpit sweat clean rocko build Jan 22 16:04:53 Does anyone know about or have a tool that can du sort on age? I'd like a tool to show me how much is in sstate cache over atime age Jan 22 16:07:12 sveinse: ls can sort by atime Jan 22 16:07:19 sveinse: i.e. ls --sort=time --time=access -l Jan 22 16:26:45 rburton, neverpanic: Ok that makes sense ... but why does autoconf work differently when I fetch the code from subversion than when I fetch it from a git repo? Jan 22 16:27:30 xthunderheartx: presumably because something else is different Jan 22 16:27:46 it seems like the configuration step would be common to/independent of both fetchers Jan 22 16:27:59 yes Jan 22 16:28:00 (it is) Jan 22 16:28:40 your RDEPENDS on dbus is redundant by the way, you'll get a proper dependency automatically from the linking Jan 22 16:29:15 xthunderheartx: maybe fetching from subversion requires a subversion client, which requires pkgconfig? Jan 22 16:29:54 ... ok. I smell smoke so I'm obviously overcooking my noodles ... Jan 22 16:31:20 K. I'll remove it from RDEPENDS. I think I snagged that from another example recipe somewhere. Jan 22 16:32:14 armpit: do we need patches in master first? Jan 22 16:32:17 I really appreciate the help. Jan 22 16:35:58 RP, yes. just the 3 glibc patches I sent yesterday Jan 22 16:37:34 armpit: do you know how can i disable or make apps configuration aware of auxiliary vector? Jan 22 16:41:07 armpit: ok, will try and get those tested with master then Jan 22 16:41:10 rburton: ^^^ Jan 22 17:11:06 hey there. Is there any way I can help in improving your infrastructure when it comes to SSL/TLS for the website? I cannot even visit the website since it _forces_ users to use unsecure TLS :( Jan 22 17:11:45 i ran into that recently, had to tweak my firefox config to allow tls v1 when i normally wouldn't, mainly for yoctoproject.org Jan 22 17:12:20 kergoth: thats why i ask to help. "tweaking" here is not an option - at all Jan 22 17:12:26 * kergoth nods Jan 22 17:14:56 sqozz: the website is being rebuilt right now so hopefully that will be solved. but halstead should know why its broken and if we can fix it now. Jan 22 17:16:09 any nice way to enable ext_attr on mkfs.ext3 in yocto 1.7.3 ? Jan 22 17:16:23 rburton, sqozz I will address the issue asap. Jan 22 17:18:14 i did a hand hack and enable that in native-sdk in /etc/mk32fs.conf but i not invoked in yocto env Jan 22 17:18:48 calling the same binary from native sdk (outside yocto) created the rootfs imgae with extended attributes Jan 22 17:18:51 rburton, halstead thx for the quick action/answer - appreciated Jan 22 17:39:41 think i can solve my problem with extended attributes with IMAGE_CMD Jan 22 17:48:43 New news from stackoverflow: Yocto/Poky: How to remove hwclock from busybox? Jan 22 18:09:50 Can anyone point me to a HOW2 or something that details how to submit a recipe to OE? I looked at the style sheet and have it formatted pretty close. Jan 22 18:10:10 Not sure what section it should be in etc. Jan 22 18:39:48 if i set IMAGE_CMD and EXTRA_IMAGECMD shoudn't I get an update create_image_ext3 script? Jan 22 18:50:54 well the script is generated but no longer created and empty partition file with dd Jan 22 19:48:25 does pseudo have anything to with mkfs.ext3 invocation ? Jan 22 19:48:56 no Jan 22 19:49:48 i called mkfs.ext3 -F -i 4096 -O ext_attr $image_path $rootfs_path ... and the resulting image did not have extended attributes Jan 22 19:50:20 and i am sure that binaries from rootfs_path have them Jan 22 19:55:11 jfyi, no packaging format supports extended attributes Jan 22 19:55:32 so if you're expecting to setattr on something in do_install then expect the attributes in the rootfs, that just won't work Jan 22 19:55:52 neither upstream rpm or dpkg or opkg support xattrs in their packages Jan 22 19:56:32 pretty sure the rootfs population code supports xattrs as i seem to recall writing that bit Jan 22 19:56:51 but you need to get the xattrs there in the first place... Jan 22 19:57:01 a postinst script is the traditional workaround Jan 22 19:57:02 rburton i am doing setcap in pkg_postinst Jan 22 19:57:14 If I am compiling a custom kernel using recipes-kernel/linux/linux-yocto-custom, where should I put my defconfig? Jan 22 19:57:44 john1987: i'd verify that the rootfs directory does have xattrs set. also is this master, rocko, or something ancient? Jan 22 19:58:08 rburton ancient..1.7.3 Jan 22 19:58:37 yeah maybe that doesn't support copying attrs Jan 22 19:59:06 rburton: the odd part : i call mkfs.ext3 outside yocto(the binary from native sdk) and that call actually created an image with xattr Jan 22 19:59:38 with the attrs you expected? Jan 22 20:00:00 rburton: capabilities Jan 22 20:00:11 weird Jan 22 20:00:21 anyway i need to walk the dogs as its 8pm :) Jan 22 20:00:48 rburton: thank you for your time Jan 22 23:12:43 Dear All, Jan 22 23:13:06 I do have a MACHINE=foo (which has all the code inplace now) Jan 22 23:13:35 now I would like to add MACHINE=bar - which has almost all the stuff as foo, with some minor tweaks (in kernel, boot sequence) Jan 22 23:14:17 Do I need to convert all foo stuff to be *.inc from *.bb and include them for those two MACHINES? Jan 22 23:14:51 or is there any more elegant way -> as to convert //aaa.txt Jan 22 23:15:12 to /foo//aaa.txt ? Jan 23 00:04:15 lukma: if you've two almost identical machines then yes an inc makes sense Jan 23 00:04:26 see how all the oe-core machines are mostly just includes of other fragments Jan 23 00:04:57 ie qemux86 includes qemu.inc then tune-i586 and sets a few varibles Jan 23 00:19:07 lukma: to add to rburton's comment, you shouldn't have to modify your recipes much or at all Jan 23 00:20:02 worst case scenario is that you go from _foo overrides to a more generic one you add to your MACHINE.inc Jan 23 00:20:31 qemuall vs qemux86 is a good example to look at **** ENDING LOGGING AT Tue Jan 23 03:00:03 2018