**** BEGIN LOGGING AT Mon Mar 07 02:59:58 2016 Mar 07 08:25:37 Hello everyone! I have a quick question: I just want to do a few quick recompiles of a kernel module. How do I keep bitbake from recompiling the complete kernel everytime I do this? I am running Angstrom 2014.12 / Yocto 1.7 Mar 07 08:39:14 good morning Mar 07 08:40:29 Spice: bitbake won't recompile all the kernel each time, is launches a make Mar 07 08:49:42 You sure? At the moment I see a 'do_compile' task running for the kernel package... Mar 07 08:51:02 I also have a very recent vmlinux and zImage in my deploy directory. Mar 07 09:00:35 What exactly does `smart upgrade` do, when it receives a SIGINT while it's running? I've tried it and to me it looks like it finnished the upgrade of the current package and then aborted Mar 07 09:01:02 But i'm reading a lot about "transactions" and that's the reason smart is so smart. Just wanted to confirm there's no kind of rollback going on Mar 07 09:03:28 Spice: if you do any modification in the kernel you get a very recent vmlinux and zImage Mar 07 09:04:03 Spice: you see a 'do_compile' task' each time because it calls make, but will compile only the modified files though Mar 07 09:11:06 hi, everyone, i am trieng apache crosscompile, i could ./configure apache successfully , but when i try running make command, i take an error: arm-poky-linux-gnueabi-gcc command not found ? Mar 07 09:11:24 actually all flags paths was exported by me Mar 07 09:32:09 kageja: have you tried exporting the sdk, and using its environment setup scripts? Mar 07 09:34:58 yes i run it Mar 07 09:35:10 LetoThe2nd: yes i run it Mar 07 09:35:35 LetoThe2nd: when i run this command echo $CC its return a true path Mar 07 09:37:47 kageja: well then maybe check existing apache recipes if it needs some additional patching. Mar 07 09:38:21 LetoThe2nd: well make shouldn't complain about missing compiler then. I guess it's another problem Mar 07 09:38:34 Anticom: erm... no. Mar 07 09:38:36 mckoan: Ok, thanks! Mar 07 09:38:38 kageja: for example did you run ./configure and make in THE SAME SHELL window after sourcing the toolchain? Mar 07 09:38:42 common mistake :> Mar 07 09:38:56 LetoThe2nd: no? Mar 07 09:39:09 Anticom: if the make uses some internal "i know better than you do" magic to tinker with paths, it easily happens. Mar 07 09:39:28 Anticom: you're right about the common mistake, thats for sure. Mar 07 09:39:39 LetoThe2nd: ah, so you're talking about patches modifying the makefile itself? Mar 07 09:40:03 Anticom: i talking about "whatever patches apache might need to properly crosscompile." Mar 07 09:40:25 hm Mar 07 09:40:26 Well I hardly ever had issues with cross compiling autotools based projects Mar 07 09:40:37 But might be. dunno Mar 07 09:40:54 Anticom: that only holds true for trivial projects, sadly. Mar 07 09:42:01 LetoThe2nd: Anticom: Ok Ok i run ./configure command and apache was configured target architecture (arm-poky-linux-gnueabi) Mar 07 09:42:30 LetoThe2nd: Anticom: Now What do i do ? Mar 07 09:42:37 make Mar 07 09:42:48 you could do make clean && make Mar 07 09:42:57 just to make sure you're not left with any crap Mar 07 09:43:18 LetoThe2nd: Antiom: which arm-poky-linux gnueabi command returns atrue patth Mar 07 09:43:33 kageja: you already told us. i listened. did you also listen what i said? Mar 07 09:44:02 ans as you can see from http://cgit.openembedded.org/meta-openembedded/tree/meta-webserver/recipes-httpd/apache2/apache2_2.4.18.bb apache needs quite a bit of additional beating to properly build. Mar 07 09:44:14 just as expected. Mar 07 09:52:29 Anticom: and if you are in for the absolute horror of autotools cross compilation, try to come up with a recipe for R. Mar 07 09:57:15 LetoThe2nd: I might take a look at it, if i got time :) Mar 07 09:57:42 Anticom: i will personally donate a crate of beer of your choice if you manage. Mar 07 09:57:59 (in a reproductible and maintainable way, of course) Mar 07 09:59:05 That sounds motivating Mar 07 10:00:06 you're welcome. Mar 07 10:00:25 Hi, if I build poky, core-image-minimal and also do -c populate_sdk, how can I add additional packages/tools into the SDK? e.g. make or the device tree compiler? Mar 07 10:00:58 cpo: well make should generally be included. Mar 07 10:01:46 cpo: in general i'd say, if you are on a recent release, have a good look at the new extensible sdk feature. Mar 07 10:02:12 im on fido Mar 07 10:02:27 IIRC fido already has it. Mar 07 10:04:18 LetoThe2nd: THX. btw, there is no make within x86_64-pokysdk-linux Mar 07 10:04:33 cpo: interesting. Mar 07 10:05:15 find . -name "*make*" returns e.g. automake but no gnu make Mar 07 10:05:35 Ill have a look at the extensible sdk feature Mar 07 10:06:08 you won't find the extensible SDK in fido I don't think; at the very least you won't find it very usable in that release Mar 07 10:06:51 bluelightning: thanks for the hint Mar 07 10:06:55 bluelightning: i remember i tried it right in dublin, and it gave mostly the results i expected. wasn't that fido? Mar 07 10:07:17 LetoThe2nd: wasn't that just after the jethro release? Mar 07 10:07:24 maybe my memory is failing Mar 07 10:07:37 bluelightning: no idea, i'm an old man and my sense of time start to be warped :P Mar 07 10:08:19 Hi o/ Mar 07 10:08:26 hmm, git branch -r --contains does indeed suggest fido had it... Mar 07 10:09:01 when I set gcc in PATH and set the LD_LIBRARY_PATH to new gcc native applications fails Mar 07 10:09:11 for example cmake-native Mar 07 10:09:18 bluelightning: my guess was that it started to be available (in whatever state) in fido Mar 07 10:09:19 it creates bootstap cmake Mar 07 10:09:34 which was build with host (from PATH gcc) Mar 07 10:09:42 it used newer glibcxx Mar 07 10:09:54 and this bootstap cmake can't find it Mar 07 10:10:15 bootstap cmake was compiled with rpath to sysroot Mar 07 10:10:27 LetoThe2nd: Now i know, what you're where talking about concerning cross compiling R... meh Mar 07 10:10:47 glibcxx is only in gcc lib directory which is different that system one Mar 07 10:10:49 Anticom: :-) Mar 07 10:11:33 do you have any proposal how to fix this ? I already created BUILD_LDFLASG_append_class-native variable and added the path to libstdc++ Mar 07 10:11:47 Anticom: don't be offended, it was just meant as an extreme example to show that just from the fact something is autotools based, there's nowhere sense in assuming crossompiliation will be less painful that any other buildsystem. Mar 07 10:12:26 i don't surrender yet. Just don't have time now to investigate any further :/ Mar 07 10:12:42 "hope dies last" *SCNR* Mar 07 10:22:51 Dunno whether that's offtopic and i don't quite know, what's going on there, but if i remove and then again install a package using smart, rpm's db to verify packages doesn't seem to update. Only if i remove the package using rpm directly and then reinstall it e.g. using smart, verify now passes Mar 07 10:22:59 Any ideas, what's going on there? Mar 07 10:27:55 Hm now it works Mar 07 10:52:53 Hello, I have a problem with using yocto on Ubuntu 15.10. I'm trying to use bitbake to compile core-image-minimal targeted to x86-64 but the compilation fails for recipe "gcc-runtime_5.3.bb, do_compile". Mar 07 10:53:46 Julius_: what is the error log, can you provide a pastebin? Mar 07 10:53:57 Yes, one minute Mar 07 10:56:13 http://pastebin.com/LqwqvhZd This is log.do_compile.26713 for gcc-runtime Mar 07 10:56:58 Julius_: we've had a similar report a few days back, its 15.10 that triggers it Mar 07 10:59:15 Okay, is there any idea on how to make it work? or should I just try to use a different dirstibution? Mar 07 10:59:28 Julius_: the simplest workaround is to build on 14.04 Mar 07 11:00:08 https://github.com/carosio/redomat <- try this ... if you know how to use docker this will give you the flexability to change distros easy Mar 07 11:00:50 wfailla: depends strongly on the use case. and package_rpm was broken for building inside docker, the lat time i checked. Mar 07 11:00:52 it takes an xml file that defines what you whant to build ... and uses a docker container to build it Mar 07 11:02:30 LetoThe2nd, I don't know about package_rpm but in his case he needs to use a different distro and just to check which one works this is faster than reinstalling Mar 07 11:03:52 docker can be a nice solution for automated/scripted builds indeed, but for ongoing development work docker is mostly unsuited. Mar 07 11:04:18 for the interactive testcase, lxc works nicer in my experience Mar 07 11:05:31 I feel like the easiest way is just to change distros at the moment, thank you so much for your help to identify the problem Mar 07 11:05:56 well we are using it to build and release caros https://github.com/carosio/caros-release Mar 07 11:07:04 just like i said... docker is great for static, repetitive tasks (which a release build certainly should be) Mar 07 11:07:05 Julius_, it was just an suggestion Mar 07 11:07:57 wfialla: I did appreciate your input, thank you Mar 07 11:08:30 LetoThe2nd, "static, repetitive tasks" yes this is exactly why using docker as a base for building poky is so elegant Mar 07 11:09:03 once yout build env is up and running commit it on to an image and start X container which all have the same base Mar 07 11:10:02 and in those containers one can build and if the build is not as you want throw away the container and get a fresh and clean build environment in a matter of seconds Mar 07 11:10:22 by starting a new docker container Mar 07 11:10:42 wfailla: nothing against that usecase. i'm just saysing that there are others too. like hands-on development of layers - there i find such things rather cumbersome. once the layers are finished, everything goes back to the build infrastructure Mar 07 11:12:03 but as always - use the tool that suits your needs best. Mar 07 11:14:35 LetoThe2nd, yes, all I what is to advertise the redomat a bit ;-) Mar 07 11:15:07 wfailla: sales provision? ;-) Mar 07 11:15:37 no its open-source ... its more like personal ego ^^ Mar 07 11:16:14 LetoThe2nd: my appologies, i dont understand what do i do ? Sorry, please you can explain step-by-step, FirstofAll i donwloaded apache2.4.18 source code and i follow this step 1--> cd /home/virtual_machine_uname/ Mar 07 11:16:14 2--> tar jxvf httpd-2.4.18.tar.bz2 Mar 07 11:16:14 3--> tar -zxvf apr-1.5.2.tar.gz Mar 07 11:16:14 4--> tar -zxvf apr-util-1.5.4.tar.gz Mar 07 11:16:14 5--> mv ./apr-1.5.2 ./httpd-2.4.18/srclib/apr Mar 07 11:16:16 6--> mv ./apr-util-1.5.4 ./httpd-2.4.18/srclib/apr-util 7-->./configure --prefix=/opt/CC_Packages_cortexa7hf_vfp_neon/httpd --with-included-apr --host=arm-poky-linux-gnueabi ap_cv_void_ptr_lt_long=8 Mar 07 11:16:35 kageja: first, please do not spam-paste in here. Mar 07 11:17:04 kageja: and no, i actually do not have the time to replicate the manual cross-build process of apache here with you. Mar 07 11:17:08 LetoThe2nd: sorry just i want to explain by myself Mar 07 11:17:27 kageja: fact: there is a recipe, in a publicly available layer. Mar 07 11:17:59 kageja: fact: this recipe brings along the needed patches and configuration options to build. Mar 07 11:18:24 kageja: hence i am not willing to invest further time as i don't see no benefit. Mar 07 11:20:53 LetoTh2nd: ok i see, but i downloaded recipes file in true folder, then i compiled yocto project for new image which has included apache server, am i right, but compiling process take too long time Mar 07 11:21:53 kageja: if your only point is trying to work around the recreation time that an OE build takes, i see even less value. Mar 07 11:36:57 kageja: http://lmgtfy.com/?q=yocto+apache+recipe Mar 07 11:40:43 Anticom: as far as i can see, he's only trying to locally work around the time that a bitbake image generation would take. Mar 07 11:41:47 LetoThe2nd: am i missing something or wouldn't `bitbake apache` be sufficient? no need to build the entire image... Mar 07 11:41:53 or whatever the recipe is called Mar 07 11:42:00 which is both a waste of time (errorprone, non-reproductible) and useless to anybody else. hence, i see no point in it. Mar 07 11:42:37 Anticom: depends on what is already there, and whatnot. maybe he doesn't even have the base build, but only a blob from somebody else. Mar 07 11:43:10 but still it doesn't make sense either way Mar 07 11:43:22 agree Mar 07 12:19:40 morning folks Mar 07 12:20:16 i've been trying to subscribe to the linux-yocto mailinglist for more than a week now :( Mar 07 12:20:27 I sent the subscription requests twice Mar 07 12:20:54 but I am not getting added to the list for some reason Mar 07 12:21:27 is there someone here who can take care of this? Mar 07 12:24:30 did you reply to the confirmation mail? Mar 07 15:40:03 Hello, I am new to yocto and failed to build the jethro release. I got errors when during do_install when it tried to chown files to root. I noticed that pseudo is disabled in meta/conf/bitbake.conf. any hints as to what I should do next? Mar 07 15:54:11 tja: it's very hard tu guess what you see there Mar 07 15:54:41 tja: pseudo is enabled for any fakeroot tasks. the fact that it's disable din bitbake.conf means nothing Mar 07 16:00:06 tja, you should probably post the recipe that cause the error + the actual error log somewhere for us to look at... Mar 07 18:28:14 here is the error from my build: ERROR: Task 1303 (/storage/home/tarcuri/src/stmp/zynq/poky-jethro-14.0.0/meta/recipes-extended/tzdata/tzdata_2015g.bb, do_install) failed with exit code '1' Mar 07 18:28:33 and I get a bunch of these: chown: changing ownership of '/storage/home/tarcuri/src/stmp/zynq/poky-jethro-14.0.0/build/tmp/work/all-poky-linux/tzdata/2015g-r0/image': Operation not permitted Mar 07 19:25:25 what' Mar 07 19:25:28 oops **** ENDING LOGGING AT Tue Mar 08 02:59:59 2016