**** BEGIN LOGGING AT Thu Nov 16 03:00:02 2017 Nov 16 07:50:48 Hello, I wanted to link to one of share object file from this recipe https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtwebengine_git.bb Nov 16 07:50:58 can any one tell me how it can be done ? Nov 16 07:56:13 New news from stackoverflow: Software watchdog causing system reboot if started at bootup Nov 16 08:18:43 how do I get/bitbake this package https://github.com/Freescale/meta-fsl-arm/tree/master/browser-layer/recipes-browser/chromium Nov 16 08:18:54 don't file its recipe file Nov 16 08:19:44 ramose_: you are using officiel nxp BSP ? Nov 16 08:21:25 nayfe: don't know have this meta-fsl-arm in my environment Nov 16 08:21:41 and I wanted to get this chromium package Nov 16 08:21:52 https://github.com/OSSystems/meta-browser it's coming from here Nov 16 08:24:50 nayfe: ok but my build env having this one chromium_48.0.2548.0.bbappend Nov 16 08:25:11 so , I probably need chromium_48.0.2548.0.bb Nov 16 08:26:40 meta-fsl-arm is an old layer, so you need to check in git history of OSS to find corresponding recipe Nov 16 08:28:51 nayfe: sorry, had to go yesterday. Thanks for letting me know. Build yet another FSL Community BSP core-image-minimal and could reproduce it too Nov 16 08:29:31 Ramose_ : you checked https://github.com/OSSystems/meta-browser/tree/krogoth/recipes-browser/chromium Nov 16 08:30:33 sagner: hey np, i think its due to new 7.5 version in rocko Nov 16 08:32:49 nayfe: yeah it seems to be incompatible on wire with everything else Nov 16 08:34:12 sagner: don't know why they switched to openssl10 instead of openssl Nov 16 08:34:17 nayfe: e.g. a Fedora 7.5 (using OpenSSL 1.1) cannot connect, or a old morty ssh client can also not connect. But two rocko 7.5 systems can talk with each other... Nov 16 08:35:27 sagner: i think it's related to cypher algorithms compatibility Nov 16 08:37:38 nayfe: I did play around with force-selecting algorithms, but it did not help (e.g. something super concervative like ssh -oCiphers=aes128-gcm@openssh.com -oMACs=hmac-sha1 lead to the same issue) Nov 16 08:40:14 actually no, that one crashed the server Nov 16 08:40:44 Alignment trap: sshd (518) PC=0x76e73378 Instr=0xecd6cb04 Address=0x76e72ca1 FSR 0x001 Nov 16 08:40:56 Unhandled fault: alignment exception (0x001) at 0x76e72ca1 Nov 16 08:41:21 sagner: lol nice! Nov 16 08:42:46 sagner: i played a bit with kexAlgorithms config then i switched to dropbear, openssh is not in my top priority todo list :p Nov 16 09:40:48 nayfe: Just added this recipe file to my env but still bitbake chromium fails Nov 16 09:43:17 Ramose_: you added the whole layer ? or just chromium_48.0.2548.0.bb file ? Nov 16 09:43:34 just recipe file Nov 16 09:45:35 : you need at least chromium.inc and chromium folder, i'd recommand you to add the layer as it is quite small (firefox&chromium) Nov 16 09:50:00 nayfe: moved to OpenSSL 1.1.0 and that seems to work Nov 16 09:51:37 nayfe: both these things are already present there Nov 16 09:52:43 its says : ERROR: Nothing PROVIDES 'chromium' Nov 16 09:53:20 sagner: nice, ping rburton ? Nov 16 09:56:49 nayfe, rburton: yeah, kicked off a ML discussion: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144513.html Nov 16 09:57:01 Ramose_> and chromium-browser.inc ? Nov 16 10:00:16 nayfe: yeah, its there as chromium-imx.inc Nov 16 10:01:34 ok, I just rectified it . Nov 16 10:06:50 but still ERROR: Nothing PROVIDES 'chromium' Nov 16 10:07:01 I have meta-fsl-arm later in bbconf too Nov 16 10:07:24 I mean this layer https://github.com/Freescale/meta-fsl-arm/tree/master/browser-layer/recipes-browser/chromium Nov 16 10:10:28 Hi all Nov 16 10:14:34 can you send ls -R Nov 16 10:19:18 https://paste.ubuntu.com/25973391/ Nov 16 10:20:18 missing https://github.com/OSSystems/meta-browser/blob/krogoth/recipes-browser/chromium/chromium.inc Nov 16 10:20:50 and https://github.com/OSSystems/meta-browser/tree/krogoth/recipes-browser/chromium/chromium all folder Nov 16 10:22:11 yeah but Nothing provides 'chromium' seems to be different issue Nov 16 10:24:11 Ramose_ nop, it's because your recipes are incomplete, so it fails to add it correctly Nov 16 10:25:23 nayfe: Actually I wanted to link "imx-vpuwrap" lib from this recipe https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtwebengine_git.bb(qtwebengine is based on chromium) Nov 16 10:26:42 New news from stackoverflow: Tomcat startup time Nov 16 10:27:01 and I don't how from recipe, one can force linking to a pariculare share object library Nov 16 10:29:15 that's totally another subject, you dont need chromium recipe to have qtwebengine working Nov 16 10:29:46 yeah Nov 16 10:29:56 may be I should try DEPENDS_append_imxvpu = " imx-vpuwrap" Nov 16 10:30:07 in qtwebengine Nov 16 10:30:10 recipe Nov 16 10:38:10 sagner: i'm Vincent Prince, we've already talked about imx usb_loader :), about openssh, ["I guess moving rocko to OpenSSL 1.1 is not really an option at this point?"] openssl 1.1 is already here in rocko, am I wrong ? so if it's broken, we should migrate ? Nov 16 10:39:39 nayfe: just answered Nov 16 10:40:50 kanavin> indeed :) thanks Nov 16 10:41:19 nayfe: last ime I tried to force 1. on people, they rebelled Nov 16 10:41:22 1.1 Nov 16 10:41:33 my current plan is to try again in the spring Nov 16 10:44:46 Hi all Nov 16 10:45:55 I've got some kind of certificate issue on a do_configure Nov 16 10:45:57 fatal: unable to access 'https://github.com/sbabic/swupdate.git/': error setting certificate verify locations: Nov 16 10:48:19 hi, which recipe version you use ? Nov 16 10:49:51 hi, I'm using rocko to build sdk for crosscompiling our application. When extract sdk build by populate_sdk I have an issue with FindQt4.cmake (we're using cmake) that it cannot find qt4 headers Nov 16 10:49:57 any ideas what to check or change? Nov 16 10:49:58 thx Nov 16 10:54:48 open-nandra: yes; port to qt5 :) but really, you need to read that .cmake file and see what it does Nov 16 10:55:43 kanavin: no thanks ;), yes I'm trying to read it and it seems to look for cmake it find but it is in x86 not crosscompiled sysroot and then it will bard that cannot find QtCore for x86 Nov 16 10:55:52 but I want to use it for crss_compilation Nov 16 10:56:09 kanavin: *qmake not cmake Nov 16 11:04:54 also qmake -query which is used to check what is installed in ointing to X86 libs + headers Nov 16 11:05:30 open-nandra: if this used to work, you need to check what has changed Nov 16 11:05:37 ok, maybe it works with 1.0.2m instead of 1.0.2l Nov 16 11:05:54 kanavinL I'm portin from morty to rocko Nov 16 11:06:00 kanavin: I'm portin from morty to rocko Nov 16 11:07:04 open-nandra: I mean run the same commands and see if they produce different outputs Nov 16 11:07:36 kanavin: which commands you mean? Nov 16 11:08:35 open-nandra: the ones that are failing for you in rocko Nov 16 11:08:58 kanavin: it's in generated SDK in rocko it works fine Nov 16 11:16:39 maybe need to poke with meta-toolchain-qte? Nov 16 11:30:22 open-nandra: then generate the sdk in morty and see how it works there Nov 16 11:30:37 kanavin: ok I'll try probably Nov 16 11:31:39 if this same thing used to work, you have the tools to find out the precise moment in space and time where it broke (git bisect, narrowing down the difference in output between working and broken) Nov 16 11:32:33 kanavin: Ok I'll try Nov 16 11:49:06 any ideas what can be causing this? ERROR: When reparsing ().../custom_image.bb.do_image_cpio, the basehash value changed from a2dadbe850a5eee53b0a6b040f647f48 to 1de9cb1d98b37f197ca50ca610352c86. The metadata is not deterministic and this needs to be fixed. Nov 16 11:49:42 nayfe: oh I see, nice meeting you here :-) Nov 16 12:04:59 I have two package as Distro_feature, ${@bb.utils.contains("DISTRO_FEATURES", "bluetooth", "packagegroup-base-bluetooth", "wifi", d)} \ Nov 16 12:05:23 how can I remove/disable bluetooth one ? Nov 16 12:08:21 Ramose_: you want to disable bluetooth entirely? how about just removing bluetooth from the DISTRO_FEATURES variable? Nov 16 12:09:16 ${@bb.utils.contains("DISTRO_FEATURES", "", "packagegroup-base-bluetooth", "wifi", d)} \ , like this ? Nov 16 12:09:54 go to your distro config file or local conf and search for DISTRO_FEATURES = "blabla" Nov 16 12:10:02 grep for DISTRO_FEATURES Nov 16 12:10:06 and just remove it from that list Nov 16 12:11:56 or can I consider this DISTRO_FEATURES_remove ? Nov 16 12:12:13 if that works for you :) Nov 16 12:13:03 aratiu: wondering if there is some kind of switch here ${@bb.utils.contains("DISTRO_FEATURES", "", "packagegroup-base-bluetooth", "wifi", d)} it self Nov 16 12:13:25 that keep wifi and disbale bluetooth Nov 16 12:13:47 you can also remove packagegroup-base-bluetooth Nov 16 12:14:08 lets they are mutully exclusive Nov 16 12:14:16 but keeping wifi is dependent on having bluetooth disabled in DISTRO_FEATURES Nov 16 12:14:30 just add the wifi to your image dependencies if you really need it Nov 16 12:17:55 aratiu: don't know how it works but you mean here ${@bb.utils.contains("DISTRO_FEATURES", "bluetooth", "packagegroup-base-bluetooth", "wifi", d)} \ wifi is dependent on having bluetooth ? Nov 16 12:18:34 nope, there wifi is added only if bluetooth is not in DISTRO_FEATURES Nov 16 12:20:35 ok, it mean if I remove bluetooth from DISTRO_FEATURE then only wifi would get in Nov 16 12:20:45 yes Nov 16 12:21:38 ok, Thanks I would try that using DISTRO_FEATURES_remove Nov 16 12:30:38 yupi I identified the problem using bitbake-diffsigs for the hash mismatch, it because of ${DATETIME} Nov 16 14:27:34 New news from stackoverflow: Detect python dependencies with yocto with setuptools Nov 16 14:56:13 nayfe: qemuarm is not affected, but ARMv7 seems to be affected, even when using qemu.. Nov 16 14:59:14 sagner: some compil flags error maybe :/ anyway i think I'll probably stick with dropbear until openssh migrates to openssl 1.1.0, another simple way could be to create a new layer meta-ssh with patched openssh ... Nov 16 17:09:04 halstead: should the f27 builder be enabled? Nov 16 17:16:28 hello Nov 16 17:16:45 is it true that when you unpack a yocto eSDK, the binaries are patched for linker paths? Nov 16 17:18:39 yeah the loader path is altered Nov 16 17:21:35 I was wondering, in systemd.bbclass, we automatically ship *.service , if i understand it correclty it is done in systemd_add_files_and_parse, where i' sure if we do the same for socket files ? how about timer files ? thanks Nov 16 17:22:07 - , where i' sure Nov 16 17:22:08 + , where i'm not sure Nov 16 17:23:14 rburton: it's not ready yet. But I'll bring it online once it is. Nov 16 17:28:29 thanks mr rburton Nov 16 17:35:16 robsta: means you can run it practically anywhere without without host distro issues Nov 16 17:54:41 RP: fair but some people don't like changing binaries Nov 16 17:54:43 (FUSA) Nov 16 17:55:13 (pesky customers) Nov 16 17:55:49 robsta: as long as you don't mind root and don't mind putting the SDK in the same location, its easy then ;-) Nov 16 17:56:35 i'm just the messenger Nov 16 17:56:59 robsta: I know. I'm just saying if you don't mind those two tradeoffs you can disable it Nov 16 18:06:09 RP, ping Nov 16 18:37:11 So replacing my libcrypto.so binary from morty fixes the issue on rocko. So I reverted openssl to morty state (1.0.2j). But this still fails... Compiler...? Nov 16 20:12:47 sagner> the only thing different from openssh 7.4 and 7.5 is this patch 0001-openssh-Fix-syntax-error-on-x32.patch Nov 16 20:13:01 sagner: and depends openssl => openssl10 Nov 16 20:16:55 let see openssl :p maybe cryptodev-linux problem Nov 16 20:26:21 nop ... maybe missing this patch file://fix-cipher-des-ede3-cfb1.patch Nov 16 20:58:46 New news from stackoverflow: core-image-minimal has bluetooth Nov 16 23:11:07 Can someone please tell me why we need this line: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image_types.bbclass?h=morty#n125 Nov 16 23:13:39 batman_: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/image_types.bbclass?h=morty&id=9ac4c8b11cd28cc1d343f9b2a91a6666febe246d? Nov 16 23:14:11 its adding a ./init symlink. are you askign why there's a init symlink at all? Nov 16 23:14:26 in which case, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/image_types.bbclass?h=morty&id=31952101f38275e0c4a8e7d6a7c5ebad452a1b5b Nov 16 23:18:54 rburton: thanks! That was my question. Is this symlink necessary? Nov 16 23:19:22 3195... has the rationale for creating it Nov 16 23:19:33 I just overrode that whole loop by setting IMAGE_BUILDING_DEBUGFS = "true" and my board still boots Nov 16 23:19:33 * armpit i'm batman Nov 16 23:19:39 heh Nov 16 23:20:10 I thought that was rostedt Nov 16 23:20:31 why isn't darknighte all up in arms ? Nov 16 23:21:27 armpit: there are many copycats, but only one darknighte. :) Nov 16 23:22:23 rburton: Thanks, I understand it now. Nov 16 23:23:35 The main problem I am facing is do_image_cpio fails with "cpio: cannot seek on output: Invalid argument" when I build rootfs > 2GB Nov 16 23:24:29 This is a limitation of cpio, where in it cant seek to the end of files bigger than 2Gb Nov 16 23:26:36 For our case, where we do SD boot. The /init symlink is not required. So I can actually add IMAGE_BUILDING_DEBUGFS = "true" and avoid the cpio seek issue Nov 17 00:59:28 New news from stackoverflow: u-boot Unknown command 'if' - try 'help' yocto Nov 17 01:48:53 Maybe this is a silly question, but what is the canonical way to make a "release" build? **** ENDING LOGGING AT Fri Nov 17 03:00:03 2017