**** BEGIN LOGGING AT Thu Jun 14 03:00:05 2018 Jun 14 03:02:56 I have selected systemd as my PREFERRED_PROVIDER_udev in my distro layer and systemd starts the system fine, however systemd does not bring up eth0. I can manually bring it up with ifup. I have also appended to ifup my /etc/network/interfaces files. What do I need to do to get systemd to bring up eth0 at boot? Jun 14 03:05:14 Guest8278: you have to add networkd see https://github.com/kraj/meta-himvis/tree/master/recipes-core/systemd Jun 14 03:05:45 you can copy that bbappend to your layer with the other files in systemd dir Jun 14 03:06:45 great, thank you Jun 14 05:09:58 good morning Jun 14 05:10:21 when trying: bitbake oracle-jse-jre Jun 14 05:10:32 i get: oracle-jse-jre was skipped: because it has a restricted license not whitelisted in LICENSE_FLAGS_WHITELIST Jun 14 05:10:50 however, in locl.conf i have this line: LICENSE_FLAGS_WHITELIST = "Oracle_Binary_Code_License_Agreement" Jun 14 05:10:58 what am i doing wrong please? Jun 14 05:11:37 poky is on sumo up to date Jun 14 05:11:46 meta-oracle-java is on master up to date Jun 14 05:12:58 did you read the docs for LICENSE_FLAGS_WHITELIST? Jun 14 05:13:09 not at all Jun 14 05:13:22 going after it now Jun 14 05:13:24 "Lists license flags that when specified in LICENSE_FLAGS within a recipe should not prevent that recipe from being built." Jun 14 05:13:39 ah Jun 14 05:13:41 man Jun 14 05:13:50 so i should just ut commercial there? Jun 14 05:14:07 let me check Jun 14 05:14:21 not sure, but seems you should use LICENSE_FLAGS as well Jun 14 05:14:35 oracle_java in this case, i think Jun 14 05:14:37 let me try Jun 14 05:16:07 that was it Jun 14 05:16:43 thank you very much lindblandro Jun 14 05:17:17 so the new list has one element: "oracle_java" Jun 14 05:18:02 np Jun 14 12:09:27 on sumo, we're facing packagegroup-machine-base not being rebuilt after kernel version bump - so bitbake fetches the .ipk from sstate, which has a hard-dep on kernel-image-4.17.0-rc5-yocto-standard, whereas we changed the kernel recipe from 4.17-rc5 to 4.17.0 Jun 14 12:10:29 looks like packagegroup-base forgets to include something in the hash computation that detects source changes ? Jun 14 12:10:51 IIRC it's intentionally not included Jun 14 12:11:12 but probably shouldn't depend on versioned package, that's a bug Jun 14 12:13:18 yann: see bd8018792155ae842952432900c8431feeaffe30 80b065ff46322ec0cad039dfd9eb2d010168dba6 commits in oe-core Jun 14 12:15:21 ok Jun 14 12:15:30 and 78cde87bb6e71ec5b603426879267874900d09f3 4aabdddf67859cd8518e5cb672fb391c859817e0 might be where the bug was introduced Jun 14 12:15:43 what's the var that names the kernel package to be pulled ? Jun 14 12:18:22 I just have this unversionned statement, and that seems to cause the package fullname to be expanded ? : MACHINE_EXTRA_RDEPENDS += "kernel-image" Jun 14 13:50:08 Hi Jun 14 13:54:23 I'm trying to get the selected image name (e.g. bitbake image-basic -> image-basic) and use "image-basic" inside a recipe. I tried with IMAGE_BASENAME but this variable is related to PN, which doesn't work. Is there a solution for that? Jun 14 14:14:54 I'm trying to get the selected image name (e.g. bitbake image-basic -> image-basic) and use "image-basic" inside a recipe. I tried with IMAGE_BASENAME but this variable is related to PN, which doesn't work. Is there a solution for that? Jun 14 14:35:51 ram0: inside a recipe that isn't the image? not possible Jun 14 14:36:03 what if i did bitbake image-basic image-another? Jun 14 14:54:21 Ok, the main problem is, that we have one machine but two kernel defconfigs. We have also multiple image. One of them image needs a different kernel defconfig. Jun 14 14:58:52 One approach was by defining a global python variable inside a image-recipe (e.g. GLOBARL_VAR = IMAGE_BASENAME) and read GLOBAL_VAR out in the machine config, where KERNEL_DEFCONFIG is definded Jun 14 15:07:11 ram0: still, in the end you're trying to pass information from a recipe to a recipe, which won't work Jun 14 15:07:42 ram0: the only way to have coherent information in two recipes is to provide it through a .conf file Jun 14 15:08:38 ram0: if you want to build two kernels then you can do that with the latest release Jun 14 15:21:25 rburton: thanks, I'm right with https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#metadata-virtual-providers ? Jun 14 16:15:25 Could I bother someone to perform a simple build (e.g. core-image-minimal) with BUILDHISTORY_FEATURES = "image package" and let me know if they are seeing a failure due to multiple recipes staging items into the same location? Jun 14 16:16:15 I was seeing this with raspberrypi0-wifi and raspberrypi2, but have a qemu-x86_64 build running now just to reduce the scope of things. Jun 14 16:19:40 Latest in the sumo branch, btw Jun 14 21:14:54 New news from stackoverflow: How to add/include altered package into final image? [Yocto Project] Jun 14 21:56:13 how to I not end up with over 1000 locale packages in a core-image-minimal-dev build ? I thought GLIBC_GENERATE_LOCALES = "en_US.UTF-8" would do it but it didn't seem to make a difference Jun 14 21:57:06 halstead, rburton: wiki plugin for the new buildbot is fixed/working! Jun 14 21:57:26 yay Jun 14 21:57:28 good work Jun 14 21:58:00 turned out a touch harder than expected Jun 14 22:06:59 rburton: we can watch https://autobuilder.yoctoproject.org/new/#/builders/30/builds/59 ... Jun 14 22:40:05 does anyone know how to stop the ^M character from being inserted into my script? I get a ^M all over my bash script files. The install script copies the entire folder cp -r ${WORKDIR}/app ${D}/app Jun 14 22:42:43 nothing is "inserting" ^M, whomever wrote the script wrote it in windows, so it's full of windows line endings Jun 14 22:43:08 worst case you can use dos2unix or frodos to convert Jun 14 22:45:14 New news from stackoverflow: BUILD_LDFLAGS set to build system libraries, not target Jun 14 22:45:36 haha mmm ... well I don't see them in the linux box I am running the build on .. let me try converting the files Jun 14 23:03:28 ran the dos2unix, but still get that same issue mmm... i guess i'll add dos2unix to the build and run it on my init script for now Jun 15 02:28:58 linuxjacques: also set IMAGE_LINGUAS = "en-us" or may be keep it empty **** ENDING LOGGING AT Fri Jun 15 03:00:10 2018