**** BEGIN LOGGING AT Wed Jun 28 03:00:05 2017 Jun 28 07:19:28 hello guys ! I have one question.. I've burned my image with yocto. After the boot and login process, I'm logged as the root user. Now I want to have a colored terminal, like the on on the standard Desktop GNU/Linux OS Jun 28 07:20:16 I thought that probably to achieve that, I need bash anc .bashrc, so I've added bash to the extra_install and gnerated the .bashrc using a txt editor Jun 28 07:20:30 by the way at login I'am always on black and white Jun 28 07:20:55 and the "echo $SHELL" returns with /bin/sh instead of /bin/bash Jun 28 07:21:08 eppak: you probably just need to enable color on the output of the programs your using... e.g. 'ls --color=auto' Jun 28 07:24:09 ty nrossi, but I intended something like https://askubuntu.com/questions/517677/how-to-get-a-colored-bash Jun 28 07:25:59 eppak: did you read the marked answer and try setting the PS1? most distro's provide a custom bash PS1 that is likely not provided by bash itself Jun 28 07:30:29 I've copied the .bashrc of a standard raspberry distribution on my poky release Jun 28 07:30:37 so that it's exaclti the same Jun 28 07:30:59 by the way the poky shell is still different from the raspberry one Jun 28 07:31:22 I 've also tried to copy the .profile Jun 28 07:31:50 the only difference I've found form now is that on raspbian echo $SHELL return /bin/bash instead of /bin/sh Jun 28 07:32:43 eppak: did you copy your "~/.bashrc" or the system/distro's bashrc in e.g. /etc/bash.bashrc? Jun 28 07:33:20 no norssi, as know i?ve copied it in both /home/root and /home/myuser Jun 28 07:33:29 I'll try now Jun 28 07:33:45 eppak: you can run /bin/bash to use to bash instead of sh. For use /bin/bash permanently and automatically, you can use usermod -s or chsh -s Jun 28 07:37:37 eppak: just note that distro's (Ubuntu, Raspbian, etc.) will provide their own customization for these configs, and they are not some sort of standard "Desktop GNU/Linux" configuration. So you will need to make the changes yourself if you want those customizations in your Yocto/OE built distro. Jun 28 07:38:05 nrossi Jun 28 07:39:21 I've edited te /etc/passwd file and changed /bin/sh to /bin/bash. now the echo $SHELL return with /bin/bash as expected Jun 28 07:40:16 regarding the customization I though that copying the raspbian .bashrc/.profile of the pi user on my system would reproduce the same terminal. by the way it's not that case Jun 28 07:40:27 What am I missing ? Jun 28 07:43:14 eppak: you will need to find where the config you are after is coming from, or an easier way is to just configure your shell how you want it (set PS1, etc in your .profile/.bashrc) Jun 28 07:48:26 thank you nrossi, you was right Jun 28 07:48:56 forcing the PS1 and some other setting in .bashrc and then sourcing it solved the issue ty Jun 28 08:12:07 good morning Jun 28 09:27:01 hello Jun 28 09:29:45 i have a file called libthing-1..-localrpm Jun 28 09:30:07 i try to use it in SRC_URI Jun 28 09:30:51 i get MAlformed URL: '-' is invalid and can not be interpreted Jun 28 09:30:59 can i somehow escape the dots? Jun 28 09:31:12 i tried \.\. but it did not help Jun 28 09:32:12 what is the exact SRC_URI you defined? Jun 28 09:33:03 SRC_URI = "\ Jun 28 09:34:08 ${SOME_VAR}/libthing-1..-local.rpm;md5=;sha256= \ Jun 28 09:34:10 " Jun 28 09:34:28 can not easily paste since it's in a different network Jun 28 09:34:35 you neecd to specify it in the format of a URI.. something like 'file://....' vs just a path.. Jun 28 09:34:47 ah Jun 28 09:34:49 greeat Jun 28 09:34:54 the system is saying that it can't be interpreted properly.. I suspect the exact error message is likely confused.. Jun 28 09:34:55 my bad :( Jun 28 09:35:03 thank you fray Jun 28 09:36:44 hmmm not, it's not this Jun 28 09:37:00 ${SOME_VAR} is in the form file://.... Jun 28 09:41:00 eek Jun 28 09:41:13 there was a '-' in the SRC_URI :( Jun 28 09:41:27 thanks again fray and sorry for the noise Jun 28 10:04:15 typicall.. '-' is allowed in a SRC_URI, as long as it's 'in the irght place'.. Jun 28 10:04:29 there are some general limits of where. Jun 28 10:14:12 it was just accidentaly placed at the beginning of a line Jun 28 10:14:18 meanwhile Jun 28 10:14:45 i have a hard time finding this: how do i tell yocto to do autporeconf --install at do_configure() time? Jun 28 10:14:52 autoreconf Jun 28 10:26:37 Hi, is yocto by any chance gonna include the microcode fix for the hyperthreading issue on intel's 6th and 7th gen? ( https://lists.debian.org/debian-devel/2017/06/msg00308.html ) . I've checked the mailing lists and there's no mention of this issue Jun 28 10:28:23 remo_: this should be handled by meta-intel: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/common/recipes-core/microcode/intel-microcode_20170511.bb?h=master Jun 28 10:29:34 found the answer in mega manual Jun 28 10:30:31 LetoThe2nd: I see, thanks. Jun 28 10:41:03 how do i tell bitbake to no longer do autoreconf --verbose --force? AUTORECON = "--install" is not helping Jun 28 10:41:13 *F Jun 28 10:46:37 hello Jun 28 10:46:47 stupid question Jun 28 10:47:45 i'm trying to find out where the recipe for doxygen is coming from, as per google it seems to be in openembedded but searching in git.openembedded.org is inconclusive Jun 28 10:57:11 robsta: https://layers.openembedded.org/layerindex/branch/master/recipes/?q=doxygen Jun 28 11:02:53 ok thanks maybe i was mislead by this https://patchwork.openembedded.org/patch/72621/ Jun 28 11:14:38 hi everyone Jun 28 11:15:20 would it be possible to build the sdk with every image build? Jun 28 11:34:15 Hello! Is there some kind of configuration to add to an image all the dev packages, the toolchain with the headers etc…? Or do I have to add each package manually? Jun 28 11:34:40 yes.. in the local.conf you can add.. Jun 28 11:34:42 (looking it up) Jun 28 11:35:22 'dev-pkgs' to the 'EXTTRA_IMAGE_FEATURES' value Jun 28 11:35:30 just search your local.conf for 'dev-pkgs' Jun 28 11:39:05 fray: thanks! I’ll try that! Jun 28 13:35:02 Maybe somebody had problem with wayland-scaner configuration on yocto? Jun 28 13:37:19 lukma: What sort of problems? Jun 28 13:38:36 jpew: it turns out that the recipe works if on HOST machine the wayland-scanner is installed at /usb/bin/wayland-scanner Jun 28 13:39:40 when there is no scanner installed in /usr/bin/wayland-scanner , build breaks Jun 28 13:39:54 The problem has been described here: Jun 28 13:39:54 https://lists.yoctoproject.org/pipermail/yocto/2016-April/029303.html Jun 28 13:40:25 but the suggested solution with PACKAGECONFIG[wayland] =modification doesn't work for me....... Jun 28 13:40:34 (as it was dedicated for Rpi) Jun 28 13:42:26 RP1: let us know if we can help on debugging something Jun 28 13:44:06 lukma: It sounds like your build doesn't know to look for wayland-scanner in the build sysroot. On the patch you referenced, it was doing that via the -DWAYLAND_SCANNER_EXECUTABLE option (the patch actually just fixes a dependency problem) Jun 28 13:44:09 I've it seems like the wayland's --with-host-scanner is enabled Jun 28 13:45:33 I've created wayland_%.bbappend Jun 28 13:45:37 with EXTRA_OECMAKE += "-DWAYLAND_SCANNER_EXECUTABLE:FILEPATH=${STAGING_BINDIR_NATIVE}/wayland-scanner" Jun 28 13:46:53 lukma: Thats a cmake thing. Wayland doesn't use cmake and won't respect that (or understand it) Jun 28 13:47:12 lukma: Is the wayland recipe itself what is failing to build? Jun 28 13:47:35 the problem is with mesa Jun 28 13:47:42 when it wants to use wayland-scanner Jun 28 13:48:30 which is provided by wayland package Jun 28 13:49:02 and uses /usr/bin/ from Host Jun 28 13:49:50 If on my build machine I have /usr/bin/wayland-scanner then it is OK, if not then build fails Jun 28 13:50:59 Ok, that a problem in the mesa recipe, not wayland. Presumably, the wayland(-native) recipe is correctly installing the build system wayland-scanner into ${STAGING_BINDIR_NATIVE}. Jun 28 13:51:06 Usually, how do you debug a problem from Makefile ? I have a problem in linking as it say that ther eis no enough room.... So I've see that there is a "build/work" dir which the works of every package. So I come to my package. I guess the "git"repo is the source. Jun 28 13:51:21 And i'm a kinda lost in that directory Jun 28 13:51:31 I don' tknow where to find the makefile for the package. Jun 28 13:52:22 jpew: The exact error when compiling mesa: Jun 28 13:52:22 | /bin/bash: /usr/bin/wayland-scanner: No such file or directory Jun 28 13:52:33 lumka: I think you need to figure out how to tell mesa the location of wayland-scanner instead of letting it guess. Jun 28 13:56:13 jpew: Ok, thanks for tip Jun 28 13:57:58 jpew: In mesa configure.ac there is --with-wayland-scanner-patch= Jun 28 14:03:54 Ya, that might be it. You also might be able to add "export WAYLAND_SCANNER=..." to the recipe. What verison of mesa are you using? Jun 28 14:09:37 hi everyone Jun 28 14:09:38 would it be possible to build the sdk with every image build? Jun 28 14:30:02 aurele: Can you clarify? Are you trying to build the SDK in the same bitbake command as the image? Jun 28 14:36:18 jpew yes Jun 28 14:36:31 jpew, exactly Jun 28 14:41:19 I don't know if you can... we just this as part of our build: bitbake image && bitbake -c populate_sdk image Jun 28 14:46:08 I would like to "deliver" the image with the fstypes and the corresponding sdk (sometimes a package could change during the first command) Jun 28 14:46:25 anyhow this is just optimization Jun 28 14:46:36 jpew, thanks for your answer Jun 28 15:46:20 aurele: you can add a DEPENDS to your image .bb that depends on a particular task... I'm not sure if you can do this for a task of your own recipe, but you can try :) Jun 28 15:47:27 boucman_work, something like DEPENDS += "do_populate_sdk" ? Jun 28 15:50:29 no, gimme a sec to check the syntax Jun 28 15:50:37 do_configure[depends] += "virtual/kernel:do_shared_workdir" Jun 28 15:51:07 jpew, boucman_work lets try this ;) Jun 28 15:52:18 what jpew said :P Jun 28 15:52:50 I don't know if do_rootfs[depends] += "...:do_populate_sysroot" would work, as it might create a circular depenency loop, but you might be able to create a new task that depends on both do_rootfs and do_populate_sysroot Jun 28 15:53:05 so in your case, you need to add to your image's .bb do_build[depends] +="your_image:do_populate_sdk" Jun 28 15:53:23 iirc do_build is the default target for a recipe... right ? Jun 28 15:53:31 jpew, boucman_work this works! Jun 28 15:53:36 :) Jun 28 15:53:38 good Jun 28 15:53:52 do_image_sdcard[depends] += "${IMAGE_BASENAME}:do_populate_sdk" Jun 28 15:54:45 Ya, I think do_build is the default... image recipes might override it to something else (if thats even possible) Jun 28 15:54:52 ${PN} might be safer than ${IMAGE_BASENAME} but both should work... Jun 28 15:54:54 I prefered to use something after the "do_rootfs" Jun 28 15:55:34 boucman_work, I will try this Jun 28 15:58:26 boucman_work, jpew thanks a lot ;) I love it Jun 28 16:22:02 hello guys !! I've a problem.. I have a yocto image with libpthread installed under /lib/ (libpthread-2.25.so) . by the way there is not /usr/include/pthread.h Jun 28 16:22:08 what have I missed ? Jun 28 16:31:58 eppak: on the target is expected to have librsries only, .h are used to build Jun 28 16:32:24 you are right ty. I've just realized Jun 28 16:32:33 eppak: this meand that you should cross-compile on the host Jun 28 16:32:45 yes Jun 28 16:32:53 ty mckoan Jun 28 16:33:02 eppak: yw Jun 28 17:07:26 eppak: you need to generate a different image which have debug symbols and libraries and headers it seems you are trying to compile something on-device Jun 28 17:07:32 is that right ? Jun 28 17:08:11 ok, I have understood now. ty khem Jun 28 17:09:24 you can do that though, see meta/recipes-extended/images/core-image-lsb-sdk.bb Jun 28 17:10:14 that will build an image which will have everything to build natively on device Jun 28 22:08:59 * kergoth grumbles Jun 28 22:30:04 any poky gurus around? Does poky force the following to errors as opposed to warnings? Jun 28 22:30:05 INSANE_SKIP_qwt_append = "already-stripped" Jun 28 22:30:05 INSANE_SKIP_libtecla_append = "ldflags" Jun 28 22:34:43 read poky.conf, look for ERROR_QA Jun 28 22:35:42 yeah, I'm being lazy Jun 28 22:35:55 crack the whip! Jun 28 22:37:08 yeah has them in ERROR_QA Jun 28 22:55:00 poky is stricter than nodistro/oe-core Jun 28 23:09:12 there, slightly less ugly Jun 28 23:09:49 Crofton|work: https://gist.github.com/kergoth/cbc491a9d1f0d5489dab1e02d5adcd19#file-notes-md Jun 28 23:10:18 potentially of interest if you end up messing with swupdate stuff again Jun 28 23:10:30 need to clean up more, add signing, and submit to meta-swupdate **** ENDING LOGGING AT Thu Jun 29 03:00:01 2017