*** trollixx <trollixx!~trollixx@sf.wisetroll.net> has left #yocto | 00:01 | |
*** trollixx <trollixx!~trollixx@sf.wisetroll.net> has joined #yocto | 00:01 | |
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 00:02 | |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 00:04 | |
-YoctoAutoBuilder- build #38 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc-lsb/builds/38 | 00:07 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 00:13 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 00:14 | |
*** sjolley <sjolley!~sjolley@134.134.139.72> has joined #yocto | 00:16 | |
*** Hodapp <Hodapp!~hodapp@72.2.112.115> has left #yocto | 00:20 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 00:23 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 00:24 | |
*** maxtothemax <maxtothemax!maxtothema@nat/intel/x-kmustbmvwlvlrehg> has quit IRC | 00:33 | |
*** yenal <yenal!~yenal@unaffiliated/yenal> has quit IRC | 00:50 | |
*** neabax <neabax!~neabax@173.247.199.210> has joined #yocto | 00:51 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 00:57 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 00:58 | |
*** mulhern <mulhern!~mulhern@50.189.153.218> has joined #yocto | 00:59 | |
*** sameo <sameo!~samuel@192.55.54.42> has quit IRC | 01:03 | |
-YoctoAutoBuilder- build #37 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/37 | 01:11 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 01:33 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 01:34 | |
*** neabax <neabax!~neabax@173.247.199.210> has quit IRC | 01:37 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 01:42 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 01:43 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 01:50 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 01:52 | |
*** behanw__ is now known as behanw | 01:53 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC | 01:55 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 01:56 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 01:57 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC | 02:01 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 02:02 | |
*** tom_say <tom_say!~tom_say@2605:6000:1403:19:223:54ff:fe82:18cc> has quit IRC | 02:08 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 02:31 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 02:32 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC | 02:39 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 02:40 | |
-YoctoAutoBuilder- build #38 of nightly-world is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/38 | 02:50 | |
*** wgao <wgao!~wgao@1.202.252.122> has quit IRC | 02:54 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC | 02:56 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 02:56 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 03:04 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 03:10 | |
*** wgao <wgao!~wgao@1.202.252.122> has joined #yocto | 03:13 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 03:19 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 03:20 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 03:29 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 03:30 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 03:38 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 03:39 | |
*** Jim__ <Jim__!411ad795@gateway/web/freenode/ip.65.26.215.149> has joined #yocto | 03:40 | |
*** Jim__ <Jim__!411ad795@gateway/web/freenode/ip.65.26.215.149> has quit IRC | 03:44 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 04:13 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 04:14 | |
*** e8johan <e8johan!~quassel@194-237-7-146.customer.telia.com> has joined #yocto | 04:20 | |
*** e8johan <e8johan!~quassel@194-237-7-146.customer.telia.com> has joined #yocto | 04:22 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 04:23 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 04:24 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 04:57 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 04:57 | |
*** agust <agust!~agust@pD9E2FBE8.dip0.t-ipconnect.de> has joined #yocto | 05:03 | |
*** roxell <roxell!~roxell@linaro/roxell> has quit IRC | 05:05 | |
*** roxell <roxell!~roxell@c-853670d5.07-21-73746f28.cust.bredbandsbolaget.se> has joined #yocto | 05:06 | |
*** roxell <roxell!~roxell@linaro/roxell> has joined #yocto | 05:06 | |
*** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 05:27 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 05:33 | |
*** rburton <rburton!~rburton@81.2.106.35> has joined #yocto | 05:38 | |
*** rburton <rburton!~rburton@81.2.106.35> has quit IRC | 05:47 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 05:48 | |
*** kbart <kbart!~KBart@213.197.143.19> has joined #yocto | 05:54 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 06:05 | |
-YoctoAutoBuilder- build #37 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/37 | 06:15 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 06:21 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 06:21 | |
*** rburton <rburton!~rburton@81.2.106.35> has joined #yocto | 06:22 | |
*** neabax <neabax!~neabax@192.77.239.84> has joined #yocto | 06:23 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 06:24 | |
*** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has quit IRC | 06:41 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC | 06:48 | |
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto | 06:49 | |
*** rburton <rburton!~rburton@81.2.106.35> has quit IRC | 06:55 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 06:55 | |
*** kroon <kroon!~kroon@193.15.174.198> has joined #yocto | 06:58 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-cwpgxjezkgzgzlpb> has joined #yocto | 06:59 | |
*** jbrianceau_away is now known as jbrianceau | 06:59 | |
*** zeeblex <zeeblex!~apalalax@134.134.137.75> has joined #yocto | 07:00 | |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 07:03 | |
*** e8johan_ <e8johan_!~quassel@194-237-7-146.customer.telia.com> has joined #yocto | 07:03 | |
*** e8johan <e8johan!~quassel@194-237-7-146.customer.telia.com> has quit IRC | 07:04 | |
*** arky <arky!~arky@197.237.140.136> has joined #yocto | 07:06 | |
*** lsb_tester <lsb_tester!~milan@111.93.218.67> has joined #yocto | 07:07 | |
lsb_tester | I am unable to install libqtopengl4 package to roofs image even with IMAGE_INSTALL_append. the RPM is available under tmp/deploy/rpm. Any idea, what's wrong ? | 07:10 |
---|---|---|
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has quit IRC | 07:11 | |
*** roric <roric!~roric@c-2d9c70d5.013-177-67626713.cust.bredbandsbolaget.se> has joined #yocto | 07:20 | |
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 07:21 | |
*** kroon <kroon!~kroon@193.15.174.198> has quit IRC | 07:26 | |
*** kroon <kroon!~kroon@193.15.174.198> has joined #yocto | 07:28 | |
*** lsb_tester <lsb_tester!~milan@111.93.218.67> has quit IRC | 07:29 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 07:29 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 07:30 | |
*** AlexG <AlexG!~ageorges@192.198.151.43> has joined #yocto | 07:31 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 07:31 | |
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:37 | |
*** florian_kc is now known as florian | 07:37 | |
*** yenal <yenal!~yenal@unaffiliated/yenal> has joined #yocto | 07:41 | |
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto | 07:41 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 07:51 | |
*** jvuo <jvuo!~jvuo@ip050-115.seclan.com> has joined #yocto | 07:51 | |
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto | 07:52 | |
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 07:58 | |
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto | 07:59 | |
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 08:04 | |
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC | 08:04 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 08:04 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 08:04 | |
*** sameo <sameo!samuel@nat/intel/x-wvgzossohexzjcjt> has joined #yocto | 08:10 | |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 08:11 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 08:13 | |
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 08:14 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 08:14 | |
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto | 08:14 | |
*** tom_say <tom_say!~tom_say@2605:6000:1403:19:223:54ff:fe82:18cc> has joined #yocto | 08:18 | |
*** Jin|away is now known as Jin^eLD | 08:27 | |
*** beaver_545 <beaver_545!~stuart@82.148.40.66> has joined #yocto | 08:28 | |
*** dv_ <dv_!~quassel@chello080108088242.14.11.vie.surfer.at> has joined #yocto | 08:36 | |
*** belen <belen!Adium@nat/intel/x-dueuhwgefmahjput> has joined #yocto | 08:45 | |
*** daemonna <daemonna!3ea85ce3@gateway/web/freenode/ip.62.168.92.227> has joined #yocto | 08:46 | |
daemonna | hi, anyone here working with ADT installer? | 08:47 |
*** neabax <neabax!~neabax@192.77.239.84> has quit IRC | 09:07 | |
*** akbennett <akbennett!akbennett@linaro/akbennett> has quit IRC | 09:09 | |
*** neabax <neabax!~neabax@192.77.239.84> has joined #yocto | 09:10 | |
*** akbennett <akbennett!akbennett@linaro/akbennett> has joined #yocto | 09:21 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 09:34 | |
*** daemonna <daemonna!3ea85ce3@gateway/web/freenode/ip.62.168.92.227> has quit IRC | 09:34 | |
*** neabax <neabax!~neabax@192.77.239.84> has quit IRC | 09:37 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 09:38 | |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has quit IRC | 09:41 | |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has joined #yocto | 09:43 | |
*** kroon <kroon!~kroon@193.15.174.198> has quit IRC | 09:44 | |
Xz | are there any plans to bump openssl version in dora? | 09:55 |
Xz | I just spotted patch on dylan to fix heartbleed on old version (1.0.1e) | 09:55 |
rburton | Xz: the dora patches were sent out last night | 10:02 |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has quit IRC | 10:05 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC | 10:08 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has joined #yocto | 10:09 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 10:14 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 10:14 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 10:14 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 10:14 | |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has joined #yocto | 10:14 | |
bluelightning | morning all | 10:21 |
*** mulhern <mulhern!~mulhern@50.189.153.218> has joined #yocto | 10:27 | |
*** RP <RP!~richard@dan.rpsys.net> has quit IRC | 10:27 | |
*** mulhern <mulhern!~mulhern@50.189.153.218> has quit IRC | 10:27 | |
*** RP <RP!~richard@5751f4a1.skybroadband.com> has joined #yocto | 10:41 | |
*** kroon <kroon!~kroon@fw.mikrodidakt.se> has joined #yocto | 10:45 | |
*** yenal <yenal!~yenal@unaffiliated/yenal> has quit IRC | 11:02 | |
*** AlexG1 <AlexG1!~ageorges@192.198.151.44> has joined #yocto | 11:02 | |
*** AlexG <AlexG!~ageorges@192.198.151.43> has quit IRC | 11:04 | |
*** yenal <yenal!~yenal@unaffiliated/yenal> has joined #yocto | 11:15 | |
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 11:15 | |
*** madhu1 <madhu1!~madhu@117.221.203.0> has joined #yocto | 11:16 | |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has joined #yocto | 11:16 | |
*** tasslehoff <tasslehoff!~tasslehof@77.40.182.98> has joined #yocto | 11:17 | |
andhe | anyone got suggestion on how to write SRC_URI to download from berlios.de? | 11:18 |
*** madhu1 <madhu1!~madhu@117.221.203.0> has quit IRC | 11:21 | |
*** zeeblex <zeeblex!~apalalax@134.134.137.75> has left #yocto | 11:27 | |
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has joined #yocto | 11:28 | |
*** AlexG1 <AlexG1!~ageorges@192.198.151.44> has quit IRC | 11:31 | |
*** AlexG <AlexG!ageorges@nat/intel/x-kxvibanblvtptben> has joined #yocto | 11:31 | |
*** madhu2 <madhu2!~madhu@117.217.254.165> has joined #yocto | 11:37 | |
xerent | any ideas on how to force a package to be rebuilt (don't cache it) ? I have some packages that are built in different configurations depending on platform, but when I build for another platform, the cached packages from the wrong platform are used. both platforms use the same recipe. | 11:39 |
*** madhu2 <madhu2!~madhu@117.217.254.165> has quit IRC | 11:41 | |
andhe | xerent: "bitbake <package> -c clean" it after build / before rebuild | 11:42 |
xerent | thanks :) | 11:43 |
kroon | -c cleansstate | 11:50 |
*** sameo <sameo!samuel@nat/intel/x-wvgzossohexzjcjt> has quit IRC | 11:50 | |
*** sameo <sameo!~samuel@192.55.54.36> has joined #yocto | 11:50 | |
*** Denwid <Denwid!c2cc4226@gateway/web/freenode/ip.194.204.66.38> has joined #yocto | 11:55 | |
Denwid | ls | 11:55 |
bluelightning | xerent: that's an indicator that the right variables are not getting into signatures for the appropriate task | 11:57 |
bluelightning | xerent: have you set PACKAGE_ARCH = "${MACHINE_ARCH}" (assuming that the recipe is machine-specific)? | 11:57 |
Denwid | ls | 11:59 |
Denwid | lsls | 11:59 |
Denwid | lol sorry :) | 12:01 |
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto | 12:05 | |
Denwid | I would like to submit a small patch to the yocto-docs, where should I send it preferrably? | 12:07 |
*** jvuo <jvuo!~jvuo@ip050-115.seclan.com> has left #yocto | 12:07 | |
Denwid | poky@yoctoproject.org ? | 12:08 |
bluelightning | Denwid: yocto@yoctoproject.org, and CC Scott Rifenbark <scott.m.rifenbark@intel.com> as well | 12:10 |
bluelightning | thanks! | 12:10 |
bluelightning | Denwid: if you could ensure [yocto-docs] is in the subject that would be great also | 12:11 |
Denwid | Cool, thanks! I will do that | 12:11 |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 12:14 | |
*** jkridner <jkridner!~jkridner@c-98-250-189-79.hsd1.mi.comcast.net> has joined #yocto | 12:14 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 12:14 | |
*** arky <arky!~arky@197.237.140.136> has quit IRC | 12:16 | |
*** jackmitchell <jackmitchell!~Thunderbi@cbnluk-gw0.cambridgebroadband.com> has quit IRC | 12:17 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 12:19 | |
*** mago_ <mago_!~mago@smtp.hms.se> has joined #yocto | 12:20 | |
*** gmacario <gmacario!~gmacario@2-225-241-33.ip178.fastwebnet.it> has joined #yocto | 12:23 | |
*** gmacario1 <gmacario1!~gmacario@2-225-241-33.ip178.fastwebnet.it> has quit IRC | 12:25 | |
*** jackmitchell <jackmitchell!~Thunderbi@cbnluk-gw0.cambridgebroadband.com> has joined #yocto | 12:25 | |
*** gmacario1 <gmacario1!~gmacario@2-225-241-33.ip178.fastwebnet.it> has joined #yocto | 12:26 | |
*** gmacario <gmacario!~gmacario@2-225-241-33.ip178.fastwebnet.it> has quit IRC | 12:27 | |
xerent | bluelightning: the architecture is one and the same for both platforms. the different platforms have similar CPU's, etc, but differ in other terms | 12:33 |
*** arky <arky!~arky@197.237.140.136> has joined #yocto | 12:33 | |
xerent | andhe: it sure rebuilds the packages after I cleaned them, but bitbake won't bake me a new image because it thinks the packages haven't changed. | 12:34 |
bluelightning | xerent: right, but if this recipe is somewhere where those differences are taken into account then you should set PACKAGE_ARCH = "${MACHINE_ARCH}" within the recipe | 12:34 |
xerent | I can't find any mention of that variable in the reference manual | 12:37 |
xerent | machine_arch that is | 12:37 |
bluelightning | xerent: you're right, I made a note | 12:37 |
bluelightning | there are lots of examples where we use that within the metadata, but then there's no way for you to know where to look for those | 12:38 |
xerent | I did know where to look: here, asking you ;) | 12:38 |
bluelightning | heh | 12:38 |
bluelightning | well it's true I don't mind helping people | 12:39 |
xerent | and a fine job you do as well | 12:39 |
bluelightning | I try | 12:39 |
xerent | now if the architectures for my different images are one and the same, how will setting the package architecture in the package recipe help? | 12:40 |
bluelightning | xerent: when you say architectures, what do you mean? | 12:40 |
bluelightning | is the MACHINE value different or the same? | 12:40 |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has quit IRC | 12:40 | |
xerent | "For example, packages can exist for the i586 or qemux86 architectures" <- Both images are built for i686 | 12:41 |
*** kevin_t <kevin_t!~Thunderbi@46.18.96.46> has joined #yocto | 12:41 | |
xerent | machine names are different | 12:41 |
xerent | as in we get images deployed to tmp/deploy/images/foo/ and tmp/deploy/images/bar/ depending on if we build a foo or a bar image | 12:42 |
bluelightning | xerent: right, but those images comprise no-architecture ("all") arch-specific ("i686") and machine-specific ("qemux86") packages | 12:42 |
bluelightning | PACKAGE_ARCH is how the system knows which one the recipe should go into | 12:43 |
bluelightning | and hence when the recipe needs rebuilding | 12:43 |
bluelightning | (and PACKAGE_ARCH = "${MACHINE}" also means it'll go into a separate workdir for each machine) | 12:43 |
xerent | do I put it into the package recipes or into the image recipe? | 12:47 |
xerent | for each package I presume | 12:48 |
bluelightning | the package recipes that are machine-specific yes | 12:48 |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 12:49 | |
bluelightning | the PACKAGE_ARCH for image recipes is already "${MACHINE_ARCH}" (and wouldn't ever be anything else - assuming they're the rootfs they're always going to be machine-specific) | 12:49 |
bluelightning | (FYI) | 12:49 |
xerent | ok, this seems to work now. thanks again for your insights | 12:50 |
xerent | do you get paid for this? | 12:50 |
xerent | you should | 12:50 |
bluelightning | I get paid to work on the Yocto Project yes | 12:51 |
xerent | great | 12:51 |
bluelightning | I wouldn't say I get paid to do support, that's something I do because I think it's important ;) | 12:51 |
xerent | I get paid to ask stupid questions ;) | 12:51 |
*** sroy_ <sroy_!~sroy@mtl.savoirfairelinux.net> has joined #yocto | 12:51 | |
*** tasslehoff <tasslehoff!~tasslehof@77.40.182.98> has quit IRC | 12:58 | |
*** arky <arky!~arky@197.237.140.136> has quit IRC | 12:59 | |
mago_ | isn't poky built on openembedded core? | 13:07 |
ndec | mago_: yes it is. | 13:08 |
ndec | poky is a reference implementation distro | 13:08 |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 13:08 | |
mago_ | shouldn't there be a layer called openembedded-core somewhere in my poky dir then? | 13:09 |
ndec | the oe-core layer is called 'meta' | 13:09 |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 13:09 | |
*** arky <arky!~arky@197.237.140.136> has joined #yocto | 13:11 | |
mago_ | ah, i see | 13:12 |
*** e8johan_ <e8johan_!~quassel@194-237-7-146.customer.telia.com> has quit IRC | 13:14 | |
mago_ | if I were to create a new distro, which shall support two custom hardware boards, should I start from yocto or base my work on openembedded-core? my two boards are based on SoCs which are supported in 2 different BSP layers already, but I need to modify the kernel and add new boards etc. Do I need to unify the kernel from both of these BSP layers and create my own kernel recipe? | 13:15 |
ndec | mago_: it depends ;-) if you make your own distro as an 'end product', i would tend to recommend to use oe-core.. but it's more a personal preference.. if you simply need to build rootfs for development and the end goal is not the distro, then poky is fine. | 13:26 |
*** belen <belen!Adium@nat/intel/x-dueuhwgefmahjput> has quit IRC | 13:28 | |
mago_ | okay. well, i would like to generate u-boot, kernel and rootfs and distribute those. I would also like to provide an SDK package and some means for users to install customized applications on their boards. In the long term, I would like to be able to distribute the whole build system so that advanced users may add custom layers etc | 13:30 |
ndec | mago_: i would personnally do it with oe-core... but you might want to hear from others too.. | 13:33 |
rburton | you can easily extend poky and tweak it, but poky is really just the confi/distro/poky.conf file so its trivial to copy the bits from that which are interesting and build your own | 13:36 |
mago_ | ok. still, the problem with the kernel remains. how would you solve it? I guess I could create an image recipe which relies on PREFERRED_PROVIDER to select virtual/kernel provider differently for each type of board? so when I build boardX, it selects kernelX to provide virtual/kernel and kernelY when I build boardY. Or is the preferred solution to create a single kernel which is capable of supporting both boards? | 13:36 |
rburton | poky really is just an example of building a distro from the pieces and something that QA use to test | 13:36 |
rburton | mago_: both are acceptable | 13:36 |
rburton | mago_: yocto's kernel builds for everything, but you can have preferred-providers per machine if you want | 13:36 |
mago_ | rburton, what do you mean "builds for everything"? | 13:37 |
*** wgao <wgao!~wgao@1.202.252.122> has quit IRC | 13:37 | |
rburton | linux-yocto can be build for all machines that oe-core/poky support | 13:37 |
rburton | and all the ones that meta-intel builds too | 13:38 |
*** wgao <wgao!~wgao@1.202.252.122> has joined #yocto | 13:38 | |
rburton | your choice really | 13:38 |
mago_ | and I can extend linux-yocto with support for my specific boards? | 13:39 |
rburton | yes | 13:39 |
rburton | some consider linux-yocto to be overly complex, but it does let you manage numerous machines and configurations relatively easy | 13:40 |
mago_ | how does the recipe handle that? do i need to supply it with patches? or in what format do i input my changes to the yocto kernel? | 13:40 |
*** wgao_ <wgao_!~wgao@1.202.252.122> has joined #yocto | 13:40 | |
*** wgao <wgao!~wgao@1.202.252.122> has quit IRC | 13:40 | |
rburton | i suggest you look at the manual for it, on the yoctoproject site | 13:41 |
mago_ | thanks | 13:41 |
*** kroon <kroon!~kroon@fw.mikrodidakt.se> has quit IRC | 13:43 | |
*** oneQubit <oneQubit!~oneQubit@c-98-231-154-140.hsd1.md.comcast.net> has quit IRC | 13:45 | |
*** oneQubit <oneQubit!~oneQubit@c-98-231-154-140.hsd1.md.comcast.net> has joined #yocto | 13:45 | |
*** AlexG1 <AlexG1!~ageorges@192.198.151.44> has joined #yocto | 13:50 | |
*** AlexG <AlexG!ageorges@nat/intel/x-kxvibanblvtptben> has quit IRC | 13:52 | |
*** codinho_ <codinho_!~me@11.99.188.90.etth.tomsknet.ru> has joined #yocto | 13:52 | |
*** AlexG1 <AlexG1!~ageorges@192.198.151.44> has quit IRC | 13:53 | |
*** AlexG <AlexG!ageorges@nat/intel/x-wgihmxubeoyhdpsl> has joined #yocto | 13:54 | |
*** reanguiano <reanguiano!~devnull@ricardoanguiano.com> has quit IRC | 13:54 | |
*** aragua <aragua!~aragua@91-224-149-44.tetaneutral.net> has joined #yocto | 13:54 | |
*** reanguiano <reanguiano!~devnull@ricardoanguiano.com> has joined #yocto | 13:55 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-mvbzpsmgotaayiae> has joined #yocto | 13:58 | |
*** dlern <dlern!~dlerner@128.224.250.2> has joined #yocto | 14:02 | |
*** oneQubit <oneQubit!~oneQubit@c-98-231-154-140.hsd1.md.comcast.net> has quit IRC | 14:05 | |
AlexVaduva | did someone of you encountered a bug like this: "error: bad value (e5500) for -mtune= switch" | 14:07 |
AlexVaduva | I encounter it when trying to build the meta-fsl-ppc b4860qds-64 kernel. | 14:07 |
AlexVaduva | any suggestions? | 14:08 |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto | 14:11 | |
*** zeeblex <zeeblex!apalalax@nat/intel/x-txmgxeyaonmuxwyb> has joined #yocto | 14:17 | |
*** belen <belen!~Adium@192.198.151.43> has joined #yocto | 14:18 | |
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 14:22 | |
*** blloyd <blloyd!~blloyd@COX-66-210-177-72-static.coxinet.net> has joined #yocto | 14:25 | |
*** kbart <kbart!~KBart@213.197.143.19> has quit IRC | 14:31 | |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 14:37 | |
*** belen1 <belen1!~Adium@192.198.151.43> has joined #yocto | 14:44 | |
*** belen <belen!~Adium@192.198.151.43> has quit IRC | 14:46 | |
*** Denwid <Denwid!c2cc4226@gateway/web/freenode/ip.194.204.66.38> has quit IRC | 14:46 | |
*** aragua <aragua!~aragua@91-224-149-44.tetaneutral.net> has quit IRC | 14:48 | |
*** belen1 <belen1!~Adium@192.198.151.43> has quit IRC | 15:00 | |
*** g1zer0 <g1zer0!~gizero@host168-65-static.12-87-b.business.telecomitalia.it> has quit IRC | 15:00 | |
*** roric <roric!~roric@c-2d9c70d5.013-177-67626713.cust.bredbandsbolaget.se> has quit IRC | 15:02 | |
*** PlkMndy <PlkMndy!PulkoMandy@78.207.238.185> has joined #yocto | 15:04 | |
*** sjolley <sjolley!~sjolley@134.134.139.72> has quit IRC | 15:09 | |
*** seezer_ <seezer_!seezer@roath.org> has joined #yocto | 15:12 | |
seezer_ | hi | 15:14 |
PlkMndy | hi there, I'm having a strange problem with a yocto build, we build an ext3 and a tar.gz rootfs, the tar is good (I can boot it over NFS) but the ext3 is broken, it's missing the /etc dir, and many binaries are installed to / instead of /usr/bin, and probably there are more issues (and of course this doesn't boot) | 15:17 |
TuTizz | hi all, what is the correct way to configure /etc/timezone? | 15:17 |
TuTizz | add tzdata to my image? | 15:17 |
PlkMndy | I'm not sure how the archive and the ext3 fs could end up being different, any hint on how the ext3 image is built? | 15:17 |
seezer_ | anyone around using qttools from meta-qt5? i need "lrelease" as build time dep in my own recipe. qttools gets build without errors - but the files split into "qttools-tools" don't get installed into sysroot. calling for DEPENDS+=qttools-tools results in "nothing provides qttools-tools". any ideas? | 15:19 |
bluelightning | seezer_: DEPENDS specifies build-time dependencies; I'm assuming qttools-tools is a runtime target so it's not valid there | 15:22 |
*** maxtothemax <maxtothemax!~maxtothem@134.134.139.76> has joined #yocto | 15:22 | |
bluelightning | TuTizz: I believe so yes | 15:23 |
TuTizz | bluelightning, ok ty | 15:23 |
bluelightning | PlkMndy: which version of the build system are you using? | 15:23 |
PlkMndy | I'm not sure, there are so much versions of everything. Does "yocto / poky / dora" answers this? | 15:25 |
*** yenal <yenal!~yenal@unaffiliated/yenal> has quit IRC | 15:26 | |
rburton | yocto is the project, poky is a reference distribution, dora is a version :) | 15:26 |
bluelightning | PlkMndy: I wonder if the filesystem is running out of space/ inodes and it's just not failing as it should | 15:27 |
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 15:28 | |
PlkMndy | [2698190.503065] EXT4-fs error (device loop0): ext4_iget:4207: inode #15236: block 1918989871: comm ls: invalid block | 15:29 |
seezer_ | bluelightning: ah you're right thanks.. qttools-native is what i was looking for | 15:29 |
PlkMndy | I get this in the syslog if I mount the rootfs | 15:29 |
PlkMndy | doesn't it recreate the rootfs from scratch at each build? do I need to clean something? | 15:30 |
*** elmi82 <elmi82!~timo@mail.bmw-carit.de> has quit IRC | 15:34 | |
bluelightning | seezer_: right yes that sounds more like it | 15:36 |
*** sjolley <sjolley!~sjolley@134.134.139.76> has joined #yocto | 15:37 | |
bluelightning | PlkMndy: you could try setting IMAGE_ROOTFS_EXTRA_SPACE to enlarge the image | 15:37 |
bluelightning | PlkMndy: I would suggest having a look at tmp/work/<machine-arch>/<image>/1.0/temp/log.do_rootfs to see if there are any obvious errors | 15:38 |
PlkMndy | I already have IMAGE_ROOTFS_EXTRA_SPACE = "50000" in the image recipe | 15:38 |
bluelightning | ah ok | 15:38 |
*** reallife <reallife!~reallife@75.127.245.90> has quit IRC | 15:44 | |
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 15:44 | |
seezer_ | bluelightning: yet i'm not quite sure how to use it from my application's build system.. i'm currently using $$[QT_INSTALL_BINS]/lrelease which resolves into "wrong" sysroot inside make.. do you happen to know how i could tackle that? | 15:45 |
Jin^eLD | hmm, whats the correct way to provide "per machine" SRC_URIs? I thought it'd be enough to have a files/$MACHINE directory and put the stuff there | 15:45 |
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has joined #yocto | 15:45 | |
bluelightning | Jin^eLD: that should work automatically, since FILESPATH gets expanded using OVERRIDES which includes ${MACHINE} | 15:46 |
bluelightning | seezer_: we do have an OE_QMAKE_LRELEASE variable that points to the lrelease binary FWIW | 15:47 |
Jin^eLD | bluelightning: would that also work with bbappend's? there is an original .bb which provides files/ntpd script, and in my bbappend I wanted to split that out into files/machine1/ntpd and filesl/machine2/ntpd and I ahve FILESEXTRAPATHS_prepend := "${THISDIR}/files:" set | 15:49 |
Jin^eLD | but in this constellation the original ntpd is taken, not the one from bbappend | 15:49 |
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has quit IRC | 15:50 | |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 15:50 | |
*** volker <volker!~quassel@host-80-81-19-29.customer.m-online.net> has quit IRC | 15:51 | |
*** reallife <reallife!~reallife@ool-4b7ff55a.static.optonline.net> has joined #yocto | 15:51 | |
bluelightning | Jin^eLD: it should, but which file is picked depends on the overrides used - if you look at log.do_fetch you can see exactly where it is looking for files | 15:54 |
seezer_ | bluelightning: i see.. but i don't have that in the run.do_compile.. is it something new or some kind of missconfiguration? | 15:54 |
bluelightning | seezer_: are you using qmake / cmake or something else? | 15:55 |
seezer_ | bluelightning: qmake yes | 15:55 |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 15:56 | |
bluelightning | seezer_: so there is code in meta/classes/qmake_base.bbclass which should hack the .pro file to point to at least the right executable name for lrelease | 15:56 |
bluelightning | if you also patch them to not use $$[QT_INSTALL_BINS] I think it should then pick up the right binary just via PATH | 15:57 |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 15:58 | |
kergoth | Hmm, where's the log for postinst intercept failures? | 16:02 |
seezer_ | bluelightning: hm strange.. the path in run.do_compile doesn't include the qt5/ subdirectory in sysroots/x86_64/usr/bin | 16:02 |
kergoth | it mentions one, but doesn't say which one to look at | 16:02 |
*** AlexG <AlexG!ageorges@nat/intel/x-wgihmxubeoyhdpsl> has quit IRC | 16:03 | |
*** zeeblex <zeeblex!apalalax@nat/intel/x-txmgxeyaonmuxwyb> has left #yocto | 16:03 | |
*** dv_ <dv_!~quassel@chello080108088242.14.11.vie.surfer.at> has quit IRC | 16:06 | |
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto | 16:06 | |
Jin^eLD | bluelightning: hmm, SRC_URI of the original recipe clearly mentions a file://ntpd, howver in log.do_fetch - I do not see this file, I do see some others though, that makes no sense... | 16:07 |
bluelightning | seezer_: it could be that that's deliberate, I had assumed that those would be in /usr/bin | 16:13 |
bluelightning | seezer_: worst case you could use sed to modify the .pro file in a do_configure_prepend() to point to ${OE_QMAKE_LRELEASE} | 16:14 |
*** belen <belen!Adium@nat/intel/x-mnugkxvjbzuefxjf> has joined #yocto | 16:14 | |
bluelightning | Jin^eLD: that sounds strange, they should match up directly | 16:14 |
Jin^eLD | bluelightning: yes... it is as if it is not in the SRC_URI at all, which makes totally no sense | 16:15 |
bluelightning | Jin^eLD: silly question, but you are looking at the right log.do_fetch - right? | 16:15 |
bluelightning | i.e. one from the same build | 16:16 |
Jin^eLD | bluelightning :) yeah I remember I had that problem once ;) I did -c devshell this time | 16:17 |
Jin^eLD | and ntpd script is actually in the original recipe in the meta layers of OE, it should be there | 16:17 |
Jin^eLD | let's see what happens if I additionally add it to the SRC_URI in my bbappend | 16:24 |
*** dmoseley <dmoseley!~dmoseley@cpe-174-096-222-251.carolina.res.rr.com> has joined #yocto | 16:27 | |
*** dv__ <dv__!~quassel@chello080108088242.14.11.vie.surfer.at> has joined #yocto | 16:29 | |
*** beaver_545 <beaver_545!~stuart@82.148.40.66> has quit IRC | 16:30 | |
seezer_ | bluelightning: problem is i don't have the OE_QMAKE_LRELEASE set here.. perhaps it's newer than my current head - i'll look into that, thank you very much | 16:30 |
Jin^eLD | bluelightning: yep, after I added it additionally in my bbappend it worked.. really strange | 16:32 |
*** seezer_ <seezer_!seezer@roath.org> has quit IRC | 16:37 | |
*** pev <pev!~pev@cpc5-trow2-0-0-cust15.18-1.cable.virginm.net> has joined #yocto | 16:45 | |
pev | Hi All, I've got a kernel recipe that *looks* like its stalling in fetch. Its supposed to just pull down a specific rev from git. I can clone the repo directly OK but when fetch looks stalled I cant see any temp download stuff under downloads. Is there any way to debug fetch better than "bitbake -v" which doesnt show anything? | 16:46 |
*** belen <belen!Adium@nat/intel/x-mnugkxvjbzuefxjf> has quit IRC | 16:48 | |
*** belen <belen!~Adium@192.198.151.43> has joined #yocto | 16:48 | |
rburton | pev: use ps and see if there's a git fetch running | 16:49 |
Jin^eLD | dss11 ist im yocto noch nicht wichtig | 16:52 |
Jin^eLD | oops wrong window | 16:52 |
*** pidge <pidge!pidge@nat/intel/x-yzhgbhccfkpbrkpv> has joined #yocto | 16:56 | |
pev | rburton: Nope, none running frustratingly | 16:59 |
*** beaver_545 <beaver_545!~stuart@host86-144-237-215.range86-144.btcentralplus.com> has joined #yocto | 17:02 | |
pev | rburton: No, i tell a lie...! | 17:03 |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto | 17:09 | |
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 17:11 | |
PlkMndy | hello again, regarding my fs corruptions issues, it looks like it's because I merged latest changes including http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dora&id=f1276b066223e7f501f7f711680215ff8edee252 | 17:22 |
PlkMndy | and this doesn't work right on an already existing image and corrupted it | 17:22 |
*** sameo <sameo!~samuel@192.55.54.36> has quit IRC | 17:23 | |
*** codinho_ <codinho_!~me@11.99.188.90.etth.tomsknet.ru> has quit IRC | 17:23 | |
*** jbrianceau is now known as jbrianceau_away | 17:25 | |
*** dv__ is now known as dv_ | 17:25 | |
-YoctoAutoBuilder- build #40 of buildtools is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/buildtools/builds/40 | 17:28 | |
-YoctoAutoBuilder- build #39 of nightly-oecore is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Building Toolchain Images_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/39 | 17:28 | |
-YoctoAutoBuilder- build #40 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/40 | 17:28 | |
-YoctoAutoBuilder- build #39 of nightly-x32 is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/39 | 17:28 | |
bluelightning | PlkMndy: I wouldn't have thought the fact that there was anything existing should make a difference | 17:28 |
bluelightning | PlkMndy: if you revert that patch does the problem go away? | 17:28 |
-YoctoAutoBuilder- build #39 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/39 | 17:28 | |
PlkMndy | yes, that was unexpected | 17:28 |
-YoctoAutoBuilder- build #39 of minnow-lsb is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/minnow-lsb/builds/39 | 17:29 | |
PlkMndy | well, I found a solution, I added RM_OLD_IMAGE to my local.conf and that fixed it | 17:29 |
-YoctoAutoBuilder- build #38 of nightly-fsl-arm is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1 BuildImages_1 BuildImages_2 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/38 | 17:29 | |
-YoctoAutoBuilder- build #40 of nightly-multilib is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/40 | 17:29 | |
PlkMndy | looking at the script that generates the ext3 fs, it tries to create an empty image by dding from /dev/null to the last block of the image | 17:29 |
-YoctoAutoBuilder- build #38 of nightly-fsl-ppc is complete: Failure [failed BuildImages Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/38 | 17:29 | |
PlkMndy | which creates an empty file of the right size if nothing exists, but doesn't clear an existing file | 17:29 |
-YoctoAutoBuilder- build #38 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/38 | 17:29 | |
PlkMndy | and then, uses mkfs on that | 17:30 |
-YoctoAutoBuilder- build #20 of nightly-ipk is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/20 | 17:30 | |
-YoctoAutoBuilder- build #38 of nightly-ppc-lsb is complete: Failure [failed BuildImages BuildImages_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/38 | 17:30 | |
-YoctoAutoBuilder- build #20 of nightly-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/20 | 17:30 | |
-YoctoAutoBuilder- build #20 of nightly-deb is complete: Failure [failed BuildImages Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/20 | 17:30 | |
-YoctoAutoBuilder- build #38 of nightly-arm-lsb is complete: Failure [failed BuildImages BuildImages_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/38 | 17:30 | |
PlkMndy | so if the image is smaller than a previous version, there could still be data from the previous image at the end of the file, for example | 17:30 |
-YoctoAutoBuilder- build #38 of nightly-mips-lsb is complete: Failure [failed BuildImages BuildImages_1 Publishing Artifacts] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/38 | 17:30 | |
bluelightning | PlkMndy: I'm a little puzzled as to why it would be looking at an existing image file to be honest | 17:31 |
bluelightning | PlkMndy: would you mind filing a bug for this? | 17:31 |
kergoth | Is Florin Sarbu on irc? | 17:31 |
PlkMndy | bluelightning: as far as I can tell, the filename for the image doesn't seem to use a timestamp, but I may be wrong | 17:32 |
bluelightning | PlkMndy: that should just be a symlink though, created after the real image | 17:32 |
bluelightning | if you mean the file in tmp/deploy anyway | 17:33 |
bluelightning | or do you mean a different file? | 17:33 |
PlkMndy | no, I mean that, but you're right | 17:35 |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC | 17:35 | |
PlkMndy | so I don't know how I ended up with persistent corruption on two different machines then | 17:36 |
*** belen <belen!~Adium@192.198.151.43> has quit IRC | 17:36 | |
bluelightning | PlkMndy: I think the bottom line is this really shouldn't be failing anywhere | 17:36 |
bluelightning | luckily the maintainer for the dora stable branch is the same person on that patch you linked, so if you can file a bug and add him (Robert Yang) on CC then he should be able to fix it | 17:37 |
* pidge kicks the autobuilder and hopes to not flood the channel again. | 17:38 | |
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has quit IRC | 17:41 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto | 17:42 | |
PlkMndy | bluelightning: I created an account at https://bugzilla.yoctoproject.org/, but I'm not sure which component to put the report in? | 17:47 |
*** gmacario1 <gmacario1!~gmacario@2-225-241-33.ip178.fastwebnet.it> has quit IRC | 17:50 | |
*** aarias <aarias!~aarias@48.Red-80-59-144.staticIP.rima-tde.net> has joined #yocto | 17:56 | |
bluelightning | PlkMndy: this would be OE-Core / Core | 17:59 |
*** aarias is now known as chesnut | 18:00 | |
*** chesnut is now known as chestnut | 18:00 | |
*** chestnut is now known as lemavo | 18:00 | |
-YoctoAutoBuilder- build #41 of buildtools is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/buildtools/builds/41 | 18:00 | |
*** aarias <aarias!~aarias@48.Red-80-59-144.staticIP.rima-tde.net> has joined #yocto | 18:01 | |
PlkMndy | https://bugzilla.yoctoproject.org/show_bug.cgi?id=6141 | 18:01 |
yocti | Bug 6141: normal, Undecided, Future, saul.wold, NEW , Rootfs ext3 filesystem was corrupt | 18:01 |
*** tobiash_ <tobiash_!~quassel@mail.bmw-carit.de> has joined #yocto | 18:03 | |
*** tobiash <tobiash!~quassel@mail.bmw-carit.de> has quit IRC | 18:03 | |
*** aarias <aarias!~aarias@48.Red-80-59-144.staticIP.rima-tde.net> has quit IRC | 18:08 | |
*** neabax <neabax!~neabax@173.247.199.210> has joined #yocto | 18:09 | |
*** maxtothemax <maxtothemax!~maxtothem@134.134.139.76> has quit IRC | 18:09 | |
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC | 18:13 | |
kergoth | Hmm, qemu-ppc crashes and burns trying to run the target binaries for p4080ds at do_rootfs time for the intercepts | 18:19 |
* kergoth digs | 18:19 | |
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has joined #yocto | 18:22 | |
*** seezer <seezer!quassel383@quassel/developer/seezer> has quit IRC | 18:24 | |
*** seezer <seezer!~seezer@quassel/developer/seezer> has joined #yocto | 18:24 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC | 18:24 | |
*** daren <daren!ada07c69@gateway/web/freenode/ip.173.160.124.105> has quit IRC | 18:26 | |
*** maxtothemax <maxtothemax!maxtothema@nat/intel/x-efrmmcfevqsjakjh> has joined #yocto | 18:27 | |
-YoctoAutoBuilder- build #40 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/40 | 18:37 | |
volker- | yocto image without samba: 42.9M, image with samba 123.7M | 18:39 |
kergoth | yikes | 18:40 |
volker- | I tried first to build samba4 myself. i gave up last night and use now 3.x from the meta-oe layer | 18:41 |
bluelightning | samba binaries are huge, yes | 18:41 |
bluelightning | last I checked it was a known problem upstream, with no plan to fix it | 18:42 |
bluelightning | not sure if samba4 fixes it, probably... | 18:42 |
volker- | it looks also like the configure script in samba3 got highly modified to get it build | 18:42 |
volker- | is there already a framework that cherry-picks recipes from other repositories? | 18:43 |
volker- | what I do right now with samba is manually copying only the two required recipes into our internal SCM | 18:44 |
bluelightning | there's combo-layer: https://wiki.yoctoproject.org/wiki/Combo-layer | 18:45 |
bluelightning | I'd be the first to admit it's a little bit fiddly though | 18:45 |
bluelightning | (and I wrote the thing...) | 18:45 |
kergoth | i doubt that does the recipe level, though | 18:45 |
*** belen <belen!~Adium@5751cae3.skybroadband.com> has joined #yocto | 18:45 | |
bluelightning | kergoth: it's not turn-key for individual recipes, but it will at least keep a directory or a wildcard matching some files up-to-date for you | 18:46 |
bluelightning | the ideal case is just to re-use the entire layer | 18:46 |
volker- | if i need more public recipes I might hack a small script, in the meantime I just do it manual. It's not complex | 18:46 |
volker- | bluelightning: teh entire layer would be much more and you never know what other side effects it might have with a higher priority | 18:47 |
bluelightning | volker-: that's the other thing, if it's just a software layer it's supposed to have no side-effects other than adding recipes | 18:47 |
kergoth | I used to use a little class that copied a recipe and its associated files into another directory, to populate a layer that was a subset of another layer. but that's because we had no other option, pre-oe-core :) | 18:48 |
bluelightning | that's still not totally true for meta-oe unfortunately :/ | 18:48 |
kergoth | nowadays layers should be fairly small and well behaved (one hopes) | 18:48 |
kergoth | indeed :\ | 18:48 |
bluelightning | maybe we'll finally get the last piece tidied up in the next cycle | 18:48 |
volker- | nothing wrong in how it is right now. I was just curious if someone did already something because it fit their own needs :) | 18:49 |
volker- | everyone has different requirements :) | 18:49 |
kergoth | we just pull in and lock down upstream layers | 18:49 |
kergoth | i expect htats what most do | 18:49 |
*** belen <belen!~Adium@5751cae3.skybroadband.com> has quit IRC | 18:49 | |
bluelightning | volker-: this particular issue is one of my pet peeves, don't worry ;) | 18:50 |
kergoth | hey, there it is! i forgot it was in oe classic. yikes, i can't say that was the greatest code | 18:50 |
* kergoth shakes head | 18:50 | |
kergoth | (http://git.openembedded.org/openembedded/tree/classes/newcollection.bbclass) | 18:50 |
volker- | I don't know if you are familiar with Chef (deployment framework). What happend there is that every cookbook (more or less a recipe group for a single task like apache, nginx, userconf) got put into its own recipe and that a framework downloads them. | 18:50 |
volker- | not what I talked about in my case, but a structure that is similar to yocto (so someone might be interested into the idea). | 18:51 |
kergoth | I think it'd be cool to have an apt-like tool that was backed by layer urls, which would "install" a recipe and its deps into a local project area, which could include fetch/unpack/patch, even, and then your builds would be against that | 18:51 |
kergoth | but obviously such a thing doesn't exist today | 18:51 |
volker- | https://gist.github.com/volker-fr/6c1308932f82b673b04a | 18:53 |
bluelightning | kergoth: interesting idea | 18:54 |
*** belen <belen!~Adium@5751cae3.skybroadband.com> has joined #yocto | 18:54 | |
kergoth | volker-: that sounds rather painful to maintain :) | 18:54 |
bluelightning | obviously something that makes maintenance harder would be a difficult sell | 18:55 |
volker- | kergoth: yeah. build a tool around it that checks for differences once in a while ;-) | 18:55 |
kergoth | it doessound like combo-layer may be your best bet at this point, if not as is, then as a starting point | 18:55 |
volker- | kergoth: I am force to use perforce and I want to have two recipes in our SCM to have it repeatable | 18:56 |
volker- | s/force/forced/ | 18:56 |
kergoth | I'd just import the entire layers, personally :) if the layers are well behaved, including them won't impact anything they shoudln't impact | 18:56 |
kergoth | and if they aren't well behaved, its a bug that should be fixed | 18:56 |
volker- | on the other side, I need to keep track of our security anyway (see OpenSSL ;-) | 18:56 |
volker- | The entire .git folder in meta-openembedded is 21M while I only need 1.2M from it (and ignore the missed history here) | 18:58 |
bluelightning | bbl | 18:59 |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 18:59 | |
-YoctoAutoBuilder- build #21 of nightly-ipk is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/21 | 19:03 | |
volker- | yeah, the combo-layer looks interesting, but it really copies everything and not just a small selection | 19:03 |
kergoth | that's what i said, and paul indicated that it can operate against a wildcard | 19:04 |
* kergoth shrugs | 19:04 | |
kergoth | never used it myself | 19:04 |
volker- | the layers.openembdedded.org does not contain all layers from git.yoctoproject.org | 19:05 |
volker- | why is that? | 19:05 |
kergoth | i doubt it was intentional, likely just an oversight | 19:06 |
kergoth | could open a big in the yocto bugzilla about it, presumably | 19:06 |
kergoth | bug | 19:06 |
*** PlkMndy <PlkMndy!PulkoMandy@78.207.238.185> has left #yocto | 19:08 | |
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto | 19:15 | |
*** kroon <kroon!~kroon@89-253-118-72.customers.ownit.se> has quit IRC | 19:16 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has quit IRC | 19:18 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has joined #yocto | 19:18 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:20 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has quit IRC | 19:24 | |
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC | 19:25 | |
*** belen <belen!~Adium@5751cae3.skybroadband.com> has quit IRC | 19:25 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-cwpgxjezkgzgzlpb> has quit IRC | 19:27 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:28 | |
*** AlexG <AlexG!42f95158@gateway/web/freenode/ip.66.249.81.88> has joined #yocto | 19:28 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:28 | |
kergoth | hey look, i reproduced the NameError: global name 'd' is not defined bug again | 19:30 |
kergoth | maybe i can finally fix that | 19:30 |
*** sgw_ <sgw_!~sgw@c-50-186-0-160.hsd1.or.comcast.net> has quit IRC | 19:30 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:31 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:31 | |
-YoctoAutoBuilder- build #21 of nightly-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/21 | 19:32 | |
-YoctoAutoBuilder- build #21 of nightly-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/21 | 19:33 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:37 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:37 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:39 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:39 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:41 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has joined #yocto | 19:41 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has quit IRC | 19:43 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has joined #yocto | 19:43 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:53 | |
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC | 19:53 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-wcabyezfwhumbmfg> has joined #yocto | 19:54 | |
*** jbrianceau_away is now known as jbrianceau_home | 19:54 | |
*** gmacario <gmacario!~gmacario@2-225-241-33.ip178.fastwebnet.it> has joined #yocto | 19:54 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 19:55 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 19:55 | |
*** wgao_ <wgao_!~wgao@1.202.252.122> has quit IRC | 19:56 | |
*** crazyl3gs <crazyl3gs!~AndChat52@188.25.132.194> has joined #yocto | 19:59 | |
*** AlexG <AlexG!42f95158@gateway/web/freenode/ip.66.249.81.88> has quit IRC | 19:59 | |
*** crazyl3gs <crazyl3gs!~AndChat52@188.25.132.194> has quit IRC | 20:00 | |
*** AlexG <AlexG!~AndChat52@188.25.132.194> has joined #yocto | 20:00 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 20:01 | |
-YoctoAutoBuilder- build #40 of minnow-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/minnow-lsb/builds/40 | 20:01 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has joined #yocto | 20:02 | |
-YoctoAutoBuilder- build #41 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/41 | 20:03 | |
*** wgao__ <wgao__!~wgao@1.202.252.122> has quit IRC | 20:03 | |
-YoctoAutoBuilder- build #39 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/39 | 20:11 | |
*** arky <arky!~arky@197.237.140.136> has quit IRC | 20:13 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has joined #yocto | 20:15 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 20:15 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 20:16 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 20:19 | |
*** sroy_ <sroy_!~sroy@mtl.savoirfairelinux.net> has quit IRC | 20:25 | |
*** crankDeric <crankDeric!~deric@204.101.219.206> has joined #yocto | 20:26 | |
crankDeric | I've got a question about pulseaudio, if I add pulseaudio to my build in conf/local.conf should I expect to see all the libs in the pulseaudio.inc recipe? I appear to be missing libpulse-simple.so and a few others, they show up in the sysroot on the build machine, but not in the sdcard image, any idea why? | 20:27 |
volker- | crankDeric: don't know how it is with pulseaudio, but the kernel does not install all the kernel modules on default it builds (at least not with the small default distro) | 20:28 |
volker- | crankDeric: with e2fsprogs I saw that you have to add the packages you need, else you don't get the fsck or mkfs automatically | 20:30 |
volker- | but I am not a yocto expert ;-) | 20:30 |
crankDeric | volker-: So I've got IMAGE_INSTALL_append = "pulseaudio" | 20:30 |
crankDeric | and if I look at the recipie for pulseaudio in the poky/meta/recipies-multimedia/pulseaudio dir theres a pulseadio.inc file | 20:30 |
crankDeric | it seems to indicate that those libs will be built, and they are, but they aren't packaged in my .sdcard, any idea how I tell Yocto to put those on my target rootfs? | 20:31 |
kergoth | crankDeric: see PACKAGES_DYNAMIC | 20:31 |
volker- | crankDeric: what I do is going into tmp/deploy/deb/*/ and look there at the packages and define them extra in IMAGE_INSTALL_append (deb because I use debian packages, yours might be different like opkg or similar) | 20:31 |
kergoth | it breaks up into many small binary packages the way kernelm-doule- does, as volker- has pointed out | 20:31 |
kergoth | pulseaudio-module-*, etc | 20:31 |
kergoth | add the ones you need to IMAGE_INSTALL | 20:31 |
crankDeric | kergoth: okay, thanks! | 20:31 |
crankDeric | volker-: thanks as well | 20:32 |
*** ant_home <ant_home!~ant__@host89-230-dynamic.20-79-r.retail.telecomitalia.it> has joined #yocto | 20:32 | |
volker- | good on the one side, bad on the other side because if you start the default one seems to be as less packages as possible and then you boot and are confused why the kernel modules and similar are not there ;-) | 20:32 |
kergoth | using granular packaging is a nice compromise solution between large images and stripping things out, since you can pull in what you need, but yeah, itd be nice if things were a little more discoverable | 20:33 |
kergoth | actually, this would be a good case to use toaster, in the future | 20:33 |
kergoth | probably | 20:33 |
*** nerdboy <nerdboy!~sarnold@dsl-66-59-252-223.static.linkline.com> has quit IRC | 20:37 | |
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 20:37 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 20:38 | |
Crofton | RP, awesome email | 20:42 |
*** crankDeric <crankDeric!~deric@204.101.219.206> has quit IRC | 20:42 | |
Crofton | we should have a discussion at OEDAM if/how "OE" can improve YP releases | 20:43 |
kergoth | I think we should branch off the release sooner, and truly make it bugfix-only at that point, avoid this last minute feature submission thing | 20:44 |
kergoth | IMO anyway | 20:44 |
volker- | kergoth: toaster? | 20:44 |
kergoth | volker-: it's the new UI for examining builds being developed. https://www.yoctoproject.org/tools-resources/projects/toaster | 20:45 |
Crofton | https://www.yoctoproject.org/blogs/belenbarrospena/2014/eye-candy | 20:45 |
kergoth | pretty cool stuff | 20:45 |
kergoth | ah yeah, thats the link i was looking for and couldn't find | 20:45 |
kergoth | thanks | 20:45 |
kergoth | hehe | 20:46 |
Crofton | I am in the process of replying to the email | 20:46 |
volker- | toaster is its own build system and not compatible with other build systems? | 20:46 |
kergoth | no, its a bitbake UI that lets you examine your bitbake builds to see how they went | 20:47 |
kergoth | it doesn't build, at this time anyway | 20:47 |
volker- | ok, just curious :) | 20:47 |
kergoth | you drop into its environment, do builds, and use toaster to look at them | 20:47 |
kergoth | afaik, anyway, i haven't used it much, just tried it once | 20:47 |
-YoctoAutoBuilder- build #39 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/39 | 20:49 | |
Crofton | I looked a little at ELCE | 20:55 |
Crofton | seems to help you get a grasp on depends | 20:56 |
kergoth | yeah, like a much, much prettier depexp + more | 20:56 |
Crofton | being a hard core gui hater, I am having a hard time figuting out why a gui will help | 20:56 |
kergoth | its one of the most common questions, so it makes a lot of sense to answer it in a way that's nice | 20:56 |
Crofton | but I also know that many customers like this stuff | 20:57 |
kergoth | personally, i want to do more work on the sub-command based ui, with whatdepends/whatprovides/etc, to answer the same questions at a commandline | 20:57 |
kergoth | but i'm anti-ui mostly too :) | 20:57 |
Crofton | and if reduces my workload, I am all for it | 20:57 |
Crofton | why do people hate rc.local now? | 20:58 |
*** mikejanzen <mikejanzen!~mikejanze@216.16.231.238> has joined #yocto | 21:03 | |
-YoctoAutoBuilder- build #39 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/39 | 21:07 | |
volker- | what is the best place to drop random recipes of? | 21:09 |
volker- | e.g. when I wrote a monit 5.8 recipe | 21:10 |
volker- | nagios has monitoring-plugins.org, chef has community.opscode.com, what does yocto have? | 21:12 |
kergoth | you can post your own layers where appropriate. meta-oe tends to get random stuff that doesn't have a real place to belong | 21:19 |
kergoth | folks often run their own meta-<username> layers for local bits | 21:19 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 21:26 | |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 21:26 | |
-YoctoAutoBuilder- build #40 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/40 | 21:28 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 21:30 | |
*** e8johan <e8johan!~quassel@90-229-157-121-no198.tbcn.telia.com> has quit IRC | 21:34 | |
*** jkridner <jkridner!~jkridner@c-98-250-189-79.hsd1.mi.comcast.net> has joined #yocto | 21:36 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 21:36 | |
regorianer | if i have a makefile which has a echo output as make all and for the install i do need to perfomr "make install", how do i configure my recipe to do this ? acutally run.do_compile calls "make" and run.do_install has nothing to do but the install_append() tuff i added on my own. | 21:36 |
-YoctoAutoBuilder- build #39 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips-lsb/builds/39 | 21:37 | |
regorianer | i could patch the makefile, but this isnt a good solution i guess | 21:37 |
regorianer | or do i just put a do_configure_append { make install } ?? | 21:38 |
volker- | kergoth: and where do I drop it off then? | 21:40 |
kergoth | I don't understand the question | 21:40 |
volker- | kergoth: if I have something and think it might be helpful for other people, where do I drop my own meta-volker off? | 21:41 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 21:42 | |
volker- | kergoth: sorry, I rephrase this, where do I "post" my own layer? | 21:42 |
kergoth | anyone can add a layer to the layer index | 21:43 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 21:43 | |
volker- | ok, excuse my question, I oversaw the "Submit layer" button :( | 21:45 |
*** pidge_ <pidge_!~pidge@134.134.139.72> has joined #yocto | 21:45 | |
*** jzhang1 <jzhang1!jzhang@nat/intel/x-nwcpevkzhqdrwued> has joined #yocto | 21:45 | |
*** jzhang <jzhang!jzhang@nat/intel/x-xejlocicbuvnvarm> has quit IRC | 21:46 | |
*** OlivierG <OlivierG!~oguiter@134.134.139.74> has joined #yocto | 21:46 | |
*** pidge <pidge!pidge@nat/intel/x-yzhgbhccfkpbrkpv> has quit IRC | 21:46 | |
*** roric <roric!~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se> has joined #yocto | 21:50 | |
kergoth | volker-: heh, np :) | 21:51 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 21:51 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 21:52 | |
*** JimBaxter <JimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 21:52 | |
*** ccaione <ccaione!~ccaione@unaffiliated/ccaione> has quit IRC | 21:58 | |
*** ant_home <ant_home!~ant__@host89-230-dynamic.20-79-r.retail.telecomitalia.it> has quit IRC | 21:59 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
-YoctoAutoBuilder- build #39 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/39 | 22:02 | |
volker- | If you do a full release, what is the most important thing beside keeping the steps repeatable (by using a local mirror, using fixed repository version/hashes)? | 22:03 |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 22:03 | |
*** ccaione <ccaione!~ccaione@unaffiliated/ccaione> has joined #yocto | 22:03 | |
volker- | How helpful is the buildhistory option? | 22:03 |
-YoctoAutoBuilder- build #41 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/41 | 22:04 | |
*** pidge_ <pidge_!~pidge@134.134.139.72> has quit IRC | 22:05 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 22:08 | |
kergoth | buildhistory is extremely useful. there's a ton of useful info in there. you can use it to compare output before and after a cahgne, to mamke sure your change didn't affect something other than what you expected, and so you can use it to monitor for image size changes more than you intend, can examine what packages are in your images, etc. i wouldn't build without it | 22:09 |
-YoctoAutoBuilder- build #39 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/39 | 22:12 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 22:17 | |
*** gmacario <gmacario!~gmacario@2-225-241-33.ip178.fastwebnet.it> has quit IRC | 22:17 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 22:18 | |
dmoseley | Does anyone have a feeling whether the patch being discussed at https://patchwork.kernel.org/patch/3926081/ will make it through LTSI and into Yocto in time for the 1.6 release? I'm tripping over that bug in one configuration and am consider submitting a bbappend to add it just in case it doesn't make it through. | 22:21 |
dmoseley | nitink: the link above ^^ is from you. | 22:23 |
*** beaver_545 <beaver_545!~stuart@host86-144-237-215.range86-144.btcentralplus.com> has quit IRC | 22:24 | |
nitink | dmoseley: that fix is already in the Yocto kernel | 22:24 |
dmoseley | Hmm. My tree must be behind. Thanks. I'll repull everything. | 22:25 |
nitink | dmoseley: right, you will need to get newer SRCREVs for kernel recipes | 22:25 |
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto | 22:25 | |
*** jbrianceau_home is now known as jbrianceau_away | 22:47 | |
*** smartin_ <smartin_!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC | 22:49 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 22:51 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 22:56 | |
*** agust <agust!~agust@pD9E2FBE8.dip0.t-ipconnect.de> has quit IRC | 22:57 | |
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC | 22:58 | |
*** sjolley <sjolley!~sjolley@134.134.139.76> has quit IRC | 23:05 | |
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-mvbzpsmgotaayiae> has quit IRC | 23:14 | |
volker- | whoever gave our build system 1GB RAM, it is not enough to handel two yocto builds at the same time... | 23:15 |
kergoth | 1gb is likely about what you need for one :) | 23:16 |
volker- | I get out of memory errors in the one case and the other case the error message is not 100% clear | 23:18 |
Crofton | rfol | 23:25 |
Crofton | I put as much ram in min eas it could hold | 23:25 |
volker- | the previous sys admins where strange. newest gear but then 8GB ram in each system. And on top of that some VMs | 23:26 |
-YoctoAutoBuilder- build #39 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm-lsb/builds/39 | 23:28 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 23:32 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 23:34 | |
*** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 23:35 | |
*** maxtothemax <maxtothemax!maxtothema@nat/intel/x-efrmmcfevqsjakjh> has quit IRC | 23:36 | |
*** Jim___ <Jim___!411ad795@gateway/web/cgi-irc/kiwiirc.com/ip.65.26.215.149> has joined #yocto | 23:45 | |
*** Squix <Squix!~Squix__@p021.net112139202.tokai.or.jp> has joined #yocto | 23:48 | |
*** sjolley <sjolley!sjolley@nat/intel/x-belihdajtxtfxrpe> has joined #yocto | 23:50 | |
dmoseley | nitink: I just pulled the latest poky and built a v3.10 kernel and it does not include that patch. Are you expecting that it's fixed in v3.10 or just v3.14? | 23:51 |
dmoseley | I used MACHINE=genericx86. | 23:51 |
nitink | dmoseley: it is fixed in v3.10, v3.14 does not have LTSI support as of now | 23:52 |
nitink | dmoseley: how are you checking whether the patch is in or not? did you try building? | 23:53 |
dmoseley | I did "bitbake -c configure linux-yocto" with PREFERRED_VERSION_blah set in my local.conf | 23:54 |
nitink | dmoseley: looks like the poky v3.10 kernel recipe need SRCREV updates to get this fix | 23:55 |
nitink | in meta-intel we get kernel version 3.10.35 | 23:56 |
nitink | in poky I am seeing version as 3.10.34 which does not have this fix | 23:56 |
dmoseley | Yeah, that's what I'm seeing. | 23:56 |
nitink | zeddii: ^^^ the v3.10 kernel recipes in the poky need srcrev updates | 23:57 |
nitink | dmoseley: zeddii sends these SRCREV updates for oecore/poky layers | 23:57 |
dmoseley | OK. Gotcha. I'll keep an eye out for it. Sounds like getting it in before 1.6 should not be a problem though. | 23:58 |
nitink | dmoseley: you can open a bug in https://bugzilla.yoctoproject.org for updation of SRCREVS of v3.10 kernels in poky/oecore | 23:59 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!