**** BEGIN LOGGING AT Wed Mar 14 03:00:01 2018 Mar 14 07:50:35 Hello ! Mar 14 09:46:13 paulbarker: I succeed ! I have a dual copy sd working with swupdate and u-boot booting to an updated rootfs ! Mar 14 10:01:46 Does anyone know if meta-freescale has a public issue tracker? Mar 14 10:04:44 I found that imx-alsa-plugins fails building when the kernel is in my workspace Mar 14 10:28:56 hi i add dropbear package on my yocto image and when i launch "bitbake core-image-minimal", i have the following error: "DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] DEBUG: Executing shell function do_compile NOTE: make -j 8 make: *** No targets. Stop. ERROR: oe_runmake failed WARNING: exit code 1 from a shell command. Mar 14 10:28:59 ERROR: Function failed: do_compile (log file is located at /home/sconte/yocto/build_yocto_labs/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/dbus/1.6.18-r0/temp/log.do_compile.20240) Mar 14 10:30:57 i look at the package dependency but dropbear doesn't need that Mar 14 10:31:38 could anyone know why l have this issue? Mar 14 10:36:23 vladzouth: Did you read the log file? Mar 14 10:47:01 this is the log file error that i report Mar 14 10:49:16 the log file contains only few line and i report this here Mar 14 10:50:46 vladzouth: What yocto distro you are working on? Did you added dropbear by IMAGE_FEATURES += "ssh-server-dropbear" ? Mar 14 10:55:14 issac_ i use daisy distro and i just add IMAGE_INSTALL_append = " dropbear" on my local.conf Mar 14 11:01:59 vladzouth: There is packagegroup-core-ssh-dropbear for dropbear too. Have you tried that? Mar 14 11:03:05 vladzouth: To see which module is depending on DBUS, run "bitbake -g " and look at the generated files Mar 14 11:05:25 i look the package dependency but there is no dbus for dropbear package Mar 14 11:06:57 vladzouth: Maybe they don't have direct dependency. Look inside the dependency file to see what package(s) depend on DBUS. Mar 14 11:08:09 how do to it? Mar 14 11:09:32 vladzouth: Run this: bitbake -g Mar 14 11:09:51 Note the "-g" flag. It generates dependency graph Mar 14 11:10:44 Look into "pn-depends.dot" and "package-depends.dot" that gets generated. They show build-time and runtime dependency respectively. Mar 14 12:31:18 quick question: is NetworkManager supposed to write an empty /etc/resolv.conf (/var/run/resolv.conf) if configured with dns=none or not touch it at all? Mar 14 12:56:11 i can't viaw the package dependencies with this method instead i use the "bitbake -g -u depexp" but there is no dependency between dropbear and dbus Mar 14 13:04:43 vladzouth: What depends on DBUS then? Mar 14 13:10:45 there is autoconf-native automake-native base-files base-passwd expat gettext-native gnu-config-native initscropts libsm libtool-cross libtool-native pkgconfig-native shadow shadow-native shadow-sysroot update-rc.d-native virtual/arm-poky-linux-gnueabi-compilerlibs virtual/arm-poky-linux-gnueabi-gcc virtual/gettext virtual/libc virtual/libintl virtual/libx11 Mar 14 13:16:49 there's the dependencies of dbus Mar 14 13:18:39 What would be the best way to view the final MACHINE_EXTRA_RDEPENDS for an image and where it was altered? Mar 14 13:18:50 bitbake -e Mar 14 13:20:56 rburton: thanks, but afaik this does not show me where the variable was altered Mar 14 13:21:56 right now I'm just looking for mentions of MACHINE_EXTRA_RDEPENDS in the sources, but I don't know which layers finaly get used and in what order Mar 14 13:22:22 ls Mar 14 13:22:45 bitbake -e shows you all modifications to a variable. it’ll have them in order in the comments, and then the final value of the variable. Mar 14 13:42:21 vladzouth: So apparently dbus was already being built, even before adding dropbear. You would mind to remove "dropbear" and run bitbake -e to see check if dbus is still present? Mar 14 14:47:45 For the record - maybe somebody would have similar problem Mar 14 14:47:53 the eSDK for proper operation Mar 14 14:48:22 requires SDK to be installed in its default location - i.e. /opt//2.4.2/ Mar 14 14:48:49 Otherwise strange errors would pop up when one wants to access nativesdk binaries - like cmake Mar 14 14:50:05 The problem is that dynamically linked nativesdk programs may need: interpreter /opt/tmp/2.4.2/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2 , which location is hardcoded Mar 14 14:51:26 lukma: they should have all been relocated Mar 14 14:51:49 the last esdk i built, about two weeks ago, was relocating fine Mar 14 14:54:43 lukma: so basically, file a bug Mar 14 15:11:54 * kergoth yawns Mar 14 15:15:14 rburton: I did :) Mar 14 15:15:37 But then thought that hardcoded paths are the default state.... Mar 14 15:16:13 rburton: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12600 Mar 14 15:16:14 Bug 12600: major, Undecided, ---, paul.eggleton, RESOLVED FIXED, nativesdk programs are not executed in eSDK Mar 14 15:16:30 shall I change the setup ? Mar 14 15:17:03 And one more thing...... for yocto 2.4.2 I've enabled eSDK updater Mar 14 15:17:28 (by setting SDK_UPDATE_URL = "http://mysite.com/sdk-updater” Mar 14 15:17:30 ) Mar 14 15:17:52 But then some errors with python3-* packages emerged Mar 14 15:18:39 It seems like some packages haven't been added (as they are now in -master branches in poky and meta-openembedded Mar 14 15:19:51 But this I need to investigate Mar 14 15:24:35 i have removed dropbear on my kernel image and i run bitbake core-image-minimal to see if everything is fine. Thank you ! Mar 14 15:36:37 lukma: if you want someone to look at it, i'd reopen it Mar 14 15:50:28 rburton: Ok Mar 14 16:47:30 If I may ask Mar 14 16:48:18 the eSDK shall be enough to work standalone ? Mar 14 16:48:23 at least for 2.4 ? Mar 14 16:48:44 not sure what you mean by work standalone, but the esdk should work yes Mar 14 16:48:48 I do have SDK_INCLUDE_TOOLCHAIN = “1” Mar 14 16:49:00 which shall allow me to include all nativesdk tools ? Mar 14 16:49:19 like eSDK is a (SDK + devtool and updater) Mar 14 16:49:30 if SDK_INCLUDE_TOOLCHAIN = “1” Mar 14 16:50:16 rburton: By work standalone I mean to just deploy eSDK Mar 14 16:56:18 also the SDK_EXT_TYPE ="full" Mar 14 17:13:54 is there an easy way to change the case of a variable or should i be using the python variable expansion Mar 14 17:24:08 are there any examples of using go-cross in recipes for golang projects that require a native library? the ones i have been able to find seem to just turn off the inclusion of the native dep and completely break the functionality it was intended to provide Mar 14 17:30:19 rozachar: to change the case of a variable's value? ${@ lets you write arbitrary python... Mar 14 17:59:27 rburton, thanks, thought there might be some other syntax to do it like in bash ${VAR^^} Mar 14 19:34:18 bueller? Mar 14 20:47:59 Maybe this is the right place to ask Mar 14 20:48:37 do you know any tool which would allow me to install linux packages with versioning? Best if it would support rpms and debs Mar 14 20:50:05 I could use yocto to download them...... Mar 14 21:42:59 lukma: dpkg and rpm? Mar 14 21:43:25 "a tool to install rpm and deb" is rpm and deb, surely. if that's not the answer then be clearer with your question. Mar 14 22:04:17 rburton: The thing is as follows Mar 14 22:04:28 I do need to install several packages along eSDK Mar 14 22:04:43 eSDK allows this - with nativesdk-XXX packages Mar 14 22:04:49 but their number is limited Mar 14 22:05:04 and it is not feasible to install GUI stuff like that Mar 14 22:05:40 the two solution which I would think of is a script bundled into eSDK Mar 14 22:06:08 which would be executed on HOST and install necessary packages Mar 14 22:06:14 (according to version) Mar 14 22:06:34 rpm and debs are two the most obvious solutions Mar 14 22:06:41 but maybe there is a better way ? Mar 15 00:52:20 Hi, I added another meta-layer where I am trying to add to oeqa, i have a /lib/oeqa/controllers path. If I include this layer, do_testimage fails complaining that it cant find module oeqa.core because its looking in my layer and not seeing a oeqa/core. pretty sure this is whats happening because if I dont include this layer in the bb file, its runs fine. think i am missing something, any ideas? **** ENDING LOGGING AT Thu Mar 15 03:00:01 2018