**** BEGIN LOGGING AT Tue Jan 05 02:59:58 2016 Jan 05 10:33:08 Hi, has anybody experience with the systemd class? I try to autoenable the service with Jan 05 10:33:08 SYSTEMD_AUTO_ENABLE_${PN}-systemd = "enable" Jan 05 10:33:08 But it wont be enabled. When looking in the systemd.bbclass there you can see the service just gets restarted in the postinst task. How is this supposed to work? Jan 05 11:06:57 could buildhistory.bbclass be used to detect package revisions (accidentally) decreasing in a neat way? i guess deliberately checking out and building old revisions would trigger it too, which might be annoying. Jan 05 11:07:14 unless some heuristic is used to try to detect that Jan 05 11:09:58 Ulfalizer: there's a qa check for that already Jan 05 11:10:26 'version-going-backwards' Jan 05 11:11:22 i'll have a look. thanks! Jan 05 11:22:40 is there some easy way to avoid large rebuilds when modifying bbclasses for debug purposes? Jan 05 14:22:22 hi, I tried yocto, but bitbacke -s crashes: http://pastebin.com/NSkrCAQR Jan 05 14:22:56 any idea what might causes this? Jan 05 14:25:20 mwarning try passing it a recipe Jan 05 14:27:54 "bitbake -c fetch strace" gives me the same error Jan 05 14:30:40 all: in the context of 'base-files' recipe, I have a few files that I would like to use instead of the ones provided by base-files recipe. e.g. I want to replace /etc/fstab and /etc/nsswitch.conf with my own version but use the rest from base-files recipe. what is the best way to do so without modifying the meta layer? Jan 05 14:32:12 all: can I achieve the above goal with a .bbappend? I have nothing to append here just repace the template files.. Jan 05 14:37:21 khem: https://autobuilder.yoctoproject.org/main/builders/ptest-x86/builds/235/steps/BuildImages/logs/stdio <— this is with your glibc 2.23 patches Jan 05 14:38:38 darkhorse_: yeah, have a bbappend with FILESEXTRAPATHS set http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-FILESEXTRAPATHS Jan 05 14:45:47 joshuag1: thanks! except that in my case my override files live in a git repo - I can't use the FILESEXTRAPATHS :( Jan 05 14:47:42 joshuag1: so I guess in the bbappend I can specify a SRC_URI to my git repo. the question then is how to tell bitbake to pick specific files from git checkout and not from template "files" directory in the base-files*.bb Jan 05 14:48:18 set FILESEXTRAPATHS to S ? Jan 05 14:48:30 * joshuagl is guessing Jan 05 14:48:56 joshuag1: ahh.. brilliant! worth trying. let me see if it works Jan 05 15:20:05 joshuagl: didn't quite work because the base-files recipe specifies full path when referring to a file e.g. in do_install(), it would say "install -m 0644 ${WORKDIR}/fstab ${D}${sysconfdir}/fstab" in which case setting FILESEXTRAPATH to ${WORKDIR}/git which contains my version of fstab file is not going to help Jan 05 15:22:14 darkhorse_: possible hack do_unpack_append () { cp ${S}/foo ${WORKDIR}/foo } ? Jan 05 15:39:49 is this the right place to ask a question about a Yocto build issue for the BeagleBone Black ? Jan 05 15:40:20 gt653: why not :) Jan 05 15:42:56 ok, I ve built an image to the BBB with qt5 in it ( with opengl enabled ). I built an app for it, but when I run it I get "failed to load driver: tilcdc", and other missing drivers Jan 05 15:43:32 does anyone know what else I need to add to the Yocto build so that I get some graphic drivers added ? Jan 05 15:44:08 gt653: what machine? the one in meta-yocto-bsp or meta-ti? Jan 05 15:44:14 what is currently in your local.conf? Jan 05 15:45:06 I didn't even use meta-ti. In the local.conf I have "MACHINE = beaglebone" Jan 05 15:46:39 I tried to add meta-ti, and then tried to add the "omap3-sgx-modules" to the "IMAGE-INSTALL.." var, but that fails to compile Jan 05 15:47:29 not sure why I tried "omap3-sgx-modules", not even sure what it does, but it sounded like it might help Jan 05 15:47:47 gt653: remove meta-yocto-bsp from your layers.conf, add meta-ti. the beagle bsp in meta-yocto-bsp is 100% open, so no GPU support Jan 05 15:50:14 what is the best way to learn yocto? I ve read the manuals and people's posts online, but there is a huge gap between that and what I need to know to do this right. For example how would I know I need to remove "meta-yocto-bsp", and add "meta-ti" instead? Jan 05 15:50:46 well you don't need to remove meta-yocto-bsp, but it does make it easier to not accidently use the wrong machine if it isn't there in the first place Jan 05 15:51:31 the basic gist is "add the machine layer, use machine layer" Jan 05 15:54:36 when you say "machine layer" do you refer to the "meta-ti" layer? Jan 05 15:55:05 yes Jan 05 15:56:56 YPTM - armin is on Jan 05 15:57:52 YPTM: Ready-Access Number: 8007302996/9139049836 Access Code: 2705751 Jan 05 15:58:00 YPTM: Stephen joined Jan 05 15:58:35 oh! Jan 05 15:59:45 YPTM: ross joined Jan 05 16:00:48 YPTM: joseppc joined Jan 05 16:00:54 YPTM: belen joined Jan 05 16:01:26 YPTM: Joshua joined Jan 05 16:03:05 YPTM: Michael here. Jan 05 16:03:38 what's going on? :S Jan 05 16:05:52 Ulfalizer: Yocto Projet Meeting. Jan 05 16:07:07 This is the once a month voice meeting for discussion with techical leads of the Yocto Project. To ask questions, etc. Jan 05 16:07:15 YPTM is: Jan 05 16:09:11 ok Jan 05 16:50:40 otavio: waaa meta-fsl-ppc is broken Jan 05 18:11:28 morning all Jan 05 19:12:42 Hi if I need to submit a patch to the yocto-kernel-tools git, whats the mailing address associated with this git? Jan 05 20:32:27 has anyone seen issues building mozjs for i586/qemux86? Jan 05 20:34:06 I get this error https://paste.fedoraproject.org/307551/14520260/ Jan 05 20:35:21 there's this line in configure.in: MOZ_FIX_LINK_PATHS='-Wl,-rpath-link,$(LIBXUL_DIST)/bin -Wl,-rpath-link,$(prefix)/lib' that ends up bein used when linkin Jan 05 20:35:55 I think that it might end up picking up libraries from the host, since prefix is /usr Jan 05 20:45:18 and it works once I hardcode -rpath-link,/lib Jan 05 20:45:44 any ideas how to nicely pass sysroot path to configure? Jan 05 20:58:01 bboozzoo: the only generic methods are to use CC, CFLAGS, etc, which we already do. you can likely just remove that -Wl,-rpath-link,$(prefix)/lib entirely. Jan 05 21:06:44 kergoth: thanks, it seems like a patch to meta-oe will be needed then Jan 05 21:17:06 this is making me feel better about my own failed build Jan 05 21:28:00 whoops Jan 05 21:28:18 well it worked locally Jan 05 21:38:05 so did mine Jan 05 21:38:19 the programmers lament Jan 05 21:56:58 anyone know what package I need to include to enable the beaglebone graphics drivers ? Jan 05 22:06:16 gt653: what do you mean? egl/gles stuff? xorg driver? Jan 05 22:08:18 the easy/fast option is fbturbo for xorg Jan 05 22:08:50 the sgx/gl stuff should be packaged Jan 05 22:09:35 if you didn't clone meta-ti you should Jan 05 22:11:15 replace the meta-yocto-bsp layer with ti bsp Jan 05 22:14:34 success! Jan 05 22:15:27 did you goose something? Jan 05 22:15:29 I already have egl/gles stuff installed but there are no drivers that would allow a graphical app to run Jan 05 22:16:29 I get "failed to load driver: tilcdc", "failed to load kms_swrast", "failed to load swrast" Jan 05 22:17:02 there is no /usr/lib/dri folder for example Jan 05 22:17:20 so I assume I must be lacking some package, thus my question Jan 05 22:17:29 I am including the meta-ti layer Jan 05 22:17:51 and removed the 'meta-yocto-bsp' folder from within meta Jan 05 22:18:42 you don't need to delete it, just take it out of bblayers.conf Jan 05 22:18:59 the dri stuff sounds like kernel config Jan 05 22:19:08 it wasn't on bblayers to start with. only meta Jan 05 22:19:19 tilcdc is a kernel module i believ Jan 05 22:19:24 +e Jan 05 22:20:12 the /dev/dri stuff will appear with the right kernel Jan 05 22:20:26 kms_swrast etc are mesa drivers Jan 05 22:20:33 I am using linux-stable 4.4 Jan 05 22:21:01 check your config for allthe ti/omap graphics stuff Jan 05 22:21:39 device drivers -> graphics -> drm, framebuffer, lcd, etc Jan 05 22:21:48 in IMAGE_INSTALL I have libgles2-mesa already Jan 05 22:22:09 where is the config exactly? Jan 05 22:22:10 depends on how things are packaged Jan 05 22:22:57 kernel defconfig is either in the recipe dir or pulled from source tree Jan 05 22:23:05 some recipes modify it Jan 05 22:23:19 depends on which kernel recipe Jan 05 22:26:21 mesa will build different drivers depending on config and video cards Jan 05 22:27:26 you can query the package manager to see what got install (also image manifest) and what files go with what packages Jan 05 22:28:09 there are also preferred_providers for opengl stuff Jan 05 22:30:12 lastly, image_install should install a package that depends on opengl stuff rather than just one mesa package (see above preferred_providers comment) Jan 05 22:33:17 set PREFERRED_PROVIDER_virtual/libgles2 if you want Jan 05 22:34:21 as in PREFERRED_PROVIDER_virtual/libgles2 = "mesa" in local.conf instead Jan 05 22:35:59 I ll try that. Jan 05 22:37:06 I looked at defconfig and I don't see what I can change that would make a difference. Jan 05 22:38:41 can you pastebin the one from your running kernel? Jan 05 22:40:26 which kernel recipe? linux-stable 4.4 is vanilla mainline? Jan 05 22:41:00 i'd go with ti-staging or robert's bb_kernel patches on mainline Jan 05 22:41:59 * nerdboy keeps hearing BBB is "mainlined" but testing reveals otherwise Jan 05 22:47:26 What's bitbake's current minimum git version? Jan 05 22:49:12 I THINk it's 1.7.8 Jan 05 22:50:09 ya.. it's 1.7.8 in YP 2.0 Jan 05 22:51:09 kergoth: I think that is somewhere in sanity.bbclass? Jan 05 22:51:29 yes.. thats where it's at Jan 05 22:51:39 def check_git_version(sanity_data): Jan 05 22:52:00 here is the pastebin for the defconfig http://pastebin.com/q0Dgp8ki Jan 05 22:52:46 kergoth: I think I've just found signs our parsing isn't deterministic :( Jan 05 22:56:30 you want it deterministic too? that costs extra... Jan 05 22:57:19 ah, I do at least understand this now... Jan 05 22:58:07 RP, we've been parsing for like 10+ years and you just figured this out? Jan 05 22:59:58 gt653: i see CONFIG_DRM_TILCDC=m and a bunch of other modules Jan 05 23:00:05 are they all loaded? Jan 05 23:01:45 please excuse my ignorance but what does "m" mean? and how do I check if they are " all loaded " Jan 05 23:02:15 get a console/shell and type lsmod Jan 05 23:03:23 you might need to add some to /etc/modules|modprobe whatever the current manual says Jan 05 23:03:41 here is the lsmod pastebin: http://pastebin.com/m91XXqNn Jan 05 23:04:15 looks like tilcdc is loaded Jan 05 23:04:27 yup Jan 05 23:04:51 try ti-staging? Jan 05 23:05:10 actually it depends on what cape/hardware support you need Jan 05 23:05:42 ti-staging has latest but not all the capes in device tree yet Jan 05 23:05:57 All I am trying to is see if I can get qt5 running on a 4dcape43t LCD screen Jan 05 23:06:05 best hardware support is still 3.14 i think Jan 05 23:06:41 so I should add "ti-staging" to the IMAGE_INSTALL var ? Jan 05 23:06:44 if it's supported in ti-staging then try building qt5 demo image Jan 05 23:07:54 no, you should put it in PREFERRED_PROVIDER_virtual/kernel Jan 05 23:09:12 read the kernel stuff in yocto manuals and kernel doc under "training" Jan 05 23:10:51 will do, in the meantime I ll launch a "ti-staging" based build Jan 05 23:11:41 for a quickie intro you could look at the crash course notes: https://github.com/VCTLabs/scale13x-presentations/blob/master/bin/yocto_scale_handout_notes.pdf Jan 05 23:12:02 has some kernel stuff plus links to references Jan 05 23:16:38 Crofton|work: I think 5 years in we discovered the order of the files on disk caused differences ;-) Jan 05 23:17:28 Crofton|work: it was a false alarm, the code parser cache was meaning I didn't see errors a clean build saw. Adding/reverting changes did weird things as the cache went hot/cold but its all understandable now and I'll stop worrying Jan 05 23:17:41 good Jan 05 23:17:51 Is there a coding style for bitbake files? (e.g. tabs vs spaces) Jan 05 23:19:18 http://openembedded.org/wiki/Styleguide Jan 05 23:19:27 Crofton|work: thank you Jan 05 23:26:34 was even updated a while back for hackerspace course Jan 05 23:27:02 * nerdboy enjoys crashing... Jan 05 23:27:25 JaMa enjoys winning Jan 05 23:33:14 the only headache in the style guide is various layers still can't agree on tabs v spaces :( **** ENDING LOGGING AT Wed Jan 06 02:59:58 2016