| 01:02.38 | *** join/#oe pompomJuice (~pompomJui@41.0.38.138) |
| 02:02.29 | *** join/#oe staylor (~staylor@S0106602ad0901f12.cg.shawcable.net) |
| 02:09.21 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
| 02:13.13 | *** join/#oe fray_ (~mhatle@192.40.192.95) |
| 02:18.49 | *** join/#oe s3v3n62mm2 (~s3v3n62mm@p3EE2FCC1.dip0.t-ipconnect.de) |
| 03:15.02 | *** join/#oe pompomJuice (~pompomJui@41.0.38.138) |
| 03:36.10 | *** join/#oe ccube (ccube@nx.mindrunner.de) |
| 03:53.42 | kergoth | I wish FILES_ supported brace expansion as well as globbing |
| 04:27.47 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 04:28.16 | *** join/#oe moto-timo (~moto-timo@196.40.10.133) |
| 04:28.40 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
| 05:19.18 | *** join/#oe clio (~andrej@85.159.109.222) |
| 05:30.14 | koen | *isgh* |
| 05:30.25 | koen | build for one machine for a while and then change to another MACHINE |
| 05:30.26 | koen | ERROR: QA Issue: Package version for package avahi-locale-zh-tw went backwards which would break package feeds from (0:0.6.31-r11.1.1 to 0:0.6.31-r11.1.0) [version-going-backwards] |
| 05:59.33 | *** join/#oe Jay7 (jay@93-81-2-15.broadband.corbina.ru) |
| 06:14.43 | *** join/#oe dlan (~dennis@gentoo/developer/dlan) |
| 06:25.58 | *** join/#oe dvhart (~dvhart@134.134.139.76) |
| 06:32.31 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
| 06:36.48 | *** join/#oe diego_r (~diego@host65-246-static.10-188-b.business.telecomitalia.it) |
| 06:50.26 | *** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se) |
| 06:53.00 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
| 06:57.28 | *** join/#oe diego_r (~diego@host65-246-static.10-188-b.business.telecomitalia.it) |
| 06:59.05 | *** join/#oe ant_work (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
| 07:02.13 | *** join/#oe tasslehoff (~Tasslehof@ti0260a430-0740.bb.online.no) |
| 07:04.13 | *** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net) |
| 07:12.16 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
| 07:17.46 | mckoan | good morning |
| 07:28.05 | *** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 07:30.47 | woglinde | gm |
| 07:31.03 | mckoan | hi woglinde |
| 07:33.25 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 07:45.53 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
| 07:50.26 | tasslehoff | morning |
| 07:50.49 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 08:08.34 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 08:08.58 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
| 08:10.55 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 08:16.39 | *** join/#oe jsea (~jsea@121.50.20.41) |
| 08:21.03 | *** join/#oe kristoffer_ (~kristoffe@ua-83-227-162-207.cust.bredbandsbolaget.se) |
| 08:21.41 | jsea | how do i declare an variable that is actually one of options that should be appended to ./configure? like --enable-blahblah |
| 08:21.54 | jsea | i mean in a recipe file |
| 08:23.41 | kroon | jsea, sounds like its PACKAGECONFIG you want |
| 08:25.27 | kroon | jsea, http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGECONFIG |
| 08:25.36 | jsea | kroon, yeah that delivers the value! thank you so much |
| 08:33.20 | *** join/#oe bluelightning (~paul@83.217.123.106) |
| 08:33.20 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 08:36.05 | bluelightning | morning all |
| 08:36.24 | woglinde | hi bluelightning |
| 08:36.29 | bluelightning | hi woglinde |
| 08:47.55 | jsea | kroon, ah I found that it worked by 'EXTRA_OECONF', not by 'PACKAGECONFIG' |
| 08:48.01 | jsea | although thank you for the help again |
| 08:51.54 | *** join/#oe roric (~roric@83.140.117.51) |
| 08:53.10 | *** join/#oe g1zer0 (~gizero@host168-65-static.12-87-b.business.telecomitalia.it) |
| 09:03.00 | *** join/#oe belen (Adium@nat/intel/x-ekejpjtkvmtacobb) |
| 09:16.55 | *** join/#oe matt10 (~matt10@65-15.80-90.static-ip.oleane.fr) |
| 09:22.12 | *** join/#oe Leatherface- (~leatherfa@2001:470:dd7d:0:2564:e902:1d37:aa8) |
| 09:54.01 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
| 09:58.41 | *** join/#oe belen (Adium@nat/intel/x-naayadgboaektxqi) |
| 10:12.15 | *** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:bd25:9aed:ec1e:701b) |
| 10:45.56 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
| 10:47.27 | *** join/#oe AlexVaduva (c1ca1642@gateway/web/freenode/ip.193.202.22.66) |
| 10:49.04 | AlexVaduva | hello guys I am trying to update the pacemaker recipe available into openembedded |
| 10:49.21 | AlexVaduva | it needed the add of libqb recipe |
| 10:50.38 | AlexVaduva | but I hit a bug into do_qa_configure: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities. Rerun configure task after fixing this. The path was '/media/sdd1/fb/alvd/lxcr-3002/build3/tmp/work/ppc7400-poky-linux/pacemaker/1.1.12-r0/pacemaker-Pacemaker-1.1.12' |
| 10:50.59 | AlexVaduva | I investigated config.log |
| 10:52.28 | mago_ | at what point does bitbake copy SRC_URI files into ${S} ? |
| 10:53.18 | AlexVaduva | there are quite more enough "unsafe for cross-compilation'" there which are identified by the insane.bbclass |
| 10:53.43 | ndec | mago_: do_fetch |
| 10:59.09 | mago_ | i'm trying to get bitbake to copy some out-of-tree C files into my ${S}, but they seem to not be copied. Are there any special rules for .c files? if I change it to a non-existing file, it stops with an error. So clearly it acknowledges the entry in SRC_URI, but for some reason it doesn't get copied to ${S} like I expect |
| 10:59.34 | mago_ | (and i'd prefer to not put in these C-files as patches) |
| 11:03.44 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 11:06.13 | bluelightning | mago_: I think you may find that they won't be copied into ${WORKDIR} until do_unpack |
| 11:33.58 | RP | mago_: They will go into ${WORKDIR}, not ${S} at do_unpack fwiw |
| 11:34.20 | mago_ | ah, yes, thank you. my mistake! it works now |
| 11:41.21 | *** join/#oe msm` (~msm@cpe-72-182-100-192.austin.res.rr.com) |
| 11:42.19 | *** join/#oe ldnunes (~ldnunes_@177.35.70.10) |
| 11:55.05 | *** join/#oe fray (U2FsdGVkX1@gate.crashing.org) |
| 12:02.36 | ndec | mago_: argh... sorry that was *my* mistake ;-) |
| 12:04.08 | pompomJuice | I am trying to create a generic recipy base.inc that contains the following for all our apps ---> RDEPENDS_${PN} += "versioninfo-package (>= ${IMAGE_BUILDNR})" |
| 12:04.14 | pompomJuice | is this the right way to achieve this? |
| 12:04.28 | pompomJuice | when I do that bitbake gives me a strange warning |
| 12:05.49 | pompomJuice | WARNING: Variable key RDEPENDS_${PN} (... all packages that include base.inc here...) replaces original key RDEPENDS_one-of-those-packages ( versioninfo-package (>= ${IMAGE_BUILDNR})). |
| 12:05.52 | pompomJuice | that is the warning |
| 12:06.33 | bluelightning | pompomJuice: are you perhaps setting RDEPENDS_<real name> = in the recipes themselves? |
| 12:06.41 | pompomJuice | yes |
| 12:06.44 | pompomJuice | after that one |
| 12:06.45 | pompomJuice | mmm |
| 12:06.50 | pompomJuice | should it always be += |
| 12:06.52 | pompomJuice | let me check |
| 12:06.59 | bluelightning | then change that to RDEPENDS_${PN} instead |
| 12:07.22 | pompomJuice | will do |
| 12:08.05 | bluelightning | or at least ${PN} based i.e. if the recipe is called bob then use RDEPENDS_${PN}-dev rather than RDEPENDS_bob-dev |
| 12:08.18 | pompomJuice | ok |
| 12:09.46 | pompomJuice | d.setVar("RDEPENDS_${PN}", " ".join(packages)) |
| 12:09.48 | pompomJuice | that line |
| 12:10.09 | pompomJuice | must be changed to append to RDEPENDS, not nuke it and start over |
| 12:10.27 | pompomJuice | damn I wish I was comfortable with python |
| 12:10.35 | pompomJuice | such a drawback with this bitbake stuff |
| 12:10.54 | pompomJuice | d.setVar("RDEPENDS_${PN}", RDEPENDS_${PN}.join(packages))? |
| 12:11.32 | pompomJuice | one-of-those-packages contained the servar, that is what the warning was about |
| 12:11.38 | pompomJuice | bitbake saw that I was nuking the variable |
| 12:11.53 | pompomJuice | it protectss me against myself.... very good :) |
| 12:12.35 | bluelightning | pompomJuice: I think what might be happening there is that ${PN} is getting expanded before the function runs |
| 12:12.50 | pompomJuice | aah |
| 12:14.48 | pompomJuice | d.setVar("RDEPENDS_${PN}", "${RDEPENDS_${PN}}".join(packages)) |
| 12:14.55 | pompomJuice | that line seems to be building... |
| 12:15.04 | pompomJuice | does it look like it does a concat? |
| 12:15.17 | pompomJuice | does .join make a space? |
| 12:15.25 | bluelightning | that is not correct I'm afraid |
| 12:15.36 | pompomJuice | im sucha python noob |
| 12:15.50 | bluelightning | it looks odd but what you call join on is the separator |
| 12:15.54 | pompomJuice | I have no idea where bitbake/bash starts and python ends in this bitbake system |
| 12:16.05 | bluelightning | so " ".join(...) joins the elements with a space |
| 12:16.18 | pompomJuice | oh |
| 12:16.20 | pompomJuice | I see |
| 12:16.32 | pompomJuice | it packs them out each with a space in between? |
| 12:16.49 | bluelightning | yes, if you call it on " " |
| 12:16.58 | pompomJuice | oh my |
| 12:17.01 | bluelightning | if you called it on ":" it would join them with a colon |
| 12:17.04 | pompomJuice | my guessing was way off |
| 12:17.15 | pompomJuice | what is the python for |
| 12:17.16 | bluelightning | but changing that isn't going to help with the issue you're having |
| 12:17.52 | pompomJuice | take whatever is in RDEPENDS_${PN} and join to it what is in packages that is seperated with that .join move |
| 12:18.01 | bluelightning | no |
| 12:18.17 | pompomJuice | is that not wat I want? |
| 12:18.41 | bluelightning | oh, if you're describing what you want, yes, sorry... I thought you were describing what it currently does |
| 12:18.44 | pompomJuice | the package that is giving the issue has a anonymouse python part that manually rigs the RDEPENDS |
| 12:19.07 | pompomJuice | it rigs with setVar |
| 12:19.12 | pompomJuice | I want to concatVAR |
| 12:19.19 | pompomJuice | how? |
| 12:19.30 | bluelightning | use appendVar ? |
| 12:19.35 | pompomJuice | well |
| 12:19.37 | pompomJuice | as I said |
| 12:19.41 | pompomJuice | noob alert |
| 12:19.46 | bluelightning | but whilst that might be desirable that isn't the issue |
| 12:19.46 | pompomJuice | let me try that |
| 12:19.54 | bluelightning | the issue as I mentioned before is that ${PN} is getting expanded before the python code runs |
| 12:20.14 | pompomJuice | aah |
| 12:20.15 | pompomJuice | I see |
| 12:20.37 | pompomJuice | ok but that pyton code is not in the base class |
| 12:20.41 | pompomJuice | or the base.inc |
| 12:20.48 | pompomJuice | it is inside one of my recipies causing the warning |
| 12:21.09 | pompomJuice | WARNING: Variable key RDEPENDS_${PN} ... replaces original key RDEPENDS_ctlab-android-apps |
| 12:21.26 | bluelightning | yes, the issue is that those are interacting poorly |
| 12:21.28 | pompomJuice | appendVar still triggers the warning |
| 12:21.32 | bluelightning | right, it would |
| 12:22.01 | pompomJuice | my tactics works for all the other recipies, just this one with the manual rigging |
| 12:22.30 | bluelightning | there are a number of ways of fixing this |
| 12:22.36 | pompomJuice | yes... |
| 12:22.58 | bluelightning | a quick hack would be to do something like d.setVar("RDEPENDS_$" + "{PN}", " ".join(packages)) |
| 12:23.44 | pompomJuice | testing |
| 12:24.43 | pompomJuice | does the same |
| 12:24.48 | pompomJuice | let me show the proper warning |
| 12:25.01 | pompomJuice | WARNING: Variable key RDEPENDS_${PN} (ctlab-osprey-android-preferences ctlab-osprey-android-configuration ctlab-osprey-android-deletedata ctlab-osprey-android-demomode ctlab-osprey-android-export ctlab-osprey-android-pqevents ctlab-osprey-android-realtimeview ctlab-osprey-android-start ctlab-osprey-android-syseventlog ctlab-osprey-android-timedrecording ctlab-osprey-android-launcher) replaces |
| 12:25.01 | pompomJuice | original key RDEPENDS_ctlab-android-apps ( duo-version (>= ${IMAGE_VERSION})). |
| 12:25.12 | pompomJuice | it notices that I replace the bottom version with the top one |
| 12:25.15 | pompomJuice | I want to append |
| 12:25.21 | pompomJuice | appendVar does not work |
| 12:25.27 | pompomJuice | your trick also |
| 12:25.30 | pompomJuice | but its a warning |
| 12:25.33 | pompomJuice | maybe it does work |
| 12:25.37 | pompomJuice | the warning might be skew |
| 12:26.29 | bluelightning | no, what it says *is* happening |
| 12:26.55 | pompomJuice | oh my |
| 12:26.56 | pompomJuice | hehe |
| 12:27.02 | bluelightning | the problem is that you're effectively setting two different variables that get combined into one later |
| 12:27.17 | bluelightning | and one just stomps on the other's value, hence the warning |
| 12:27.36 | pompomJuice | I dont want stomping |
| 12:27.42 | pompomJuice | I want to combine |
| 12:27.45 | bluelightning | no, which is why you need to fix the issue |
| 12:28.03 | pompomJuice | the duo-version one I want appended to whatever is already in RDEPENDS_${PN} for that recipy |
| 12:29.04 | pompomJuice | I see this convention in my recipy ->>> python __anonymous () { |
| 12:29.14 | pompomJuice | what does that do? |
| 12:29.17 | pompomJuice | where does it hook in |
| 12:29.48 | bluelightning | it just gets run during parsing |
| 12:29.57 | pompomJuice | before or after |
| 12:29.59 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 12:30.08 | bluelightning | http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#anonymous-python-functions |
| 12:33.12 | pompomJuice | I might have a solution |
| 12:33.55 | *** join/#oe clio (~andrej@85.159.109.222) |
| 12:34.20 | pompomJuice | basically specify another variable in the anon python that is used inside the recipy to do the combine there with a += |
| 12:34.42 | pompomJuice | your anon python documentation fixed the problem |
| 12:34.56 | bluelightning | yep, that's another way to do it |
| 12:34.57 | pompomJuice | now I understand how that works |
| 12:35.15 | pompomJuice | thanks man |
| 12:47.38 | mago_ | i don't fully understand how to manage my patches with bitbake. lets say i make a patch (#1). now, i want to make another patch (#2), so i enter the ${S} dir (which is a git repo in my case). It is dirty, since patch #1 has been applied. am I suppose to make my changes and create a new patch to replace #1, or should I first do a dummy commit of the dirty tree, make my changes, commit it and finally generate #2? if I have like 5 patches on a repo, t |
| 12:47.38 | mago_ | his process becomes quite frustrating .. |
| 12:48.01 | *** join/#oe CMoH (~cipi@unaffiliated/c-moh) |
| 12:48.41 | pompomJuice | the way I do it is as follows |
| 12:48.45 | pompomJuice | bitbake foo -c patch |
| 12:48.50 | pompomJuice | go to the workdir |
| 12:49.00 | pompomJuice | quilt new somepatch.patch |
| 12:49.04 | pompomJuice | quilt add somefile |
| 12:49.09 | pompomJuice | edit somefile |
| 12:49.14 | pompomJuice | quilt refresh |
| 12:49.25 | pompomJuice | copy the somepatch.patch file to your recipies |
| 12:49.39 | pompomJuice | anything else is going to be hard |
| 12:49.41 | ndec | yes, that's the right way to do it, actually. |
| 12:50.01 | ndec | bitbake will manage/apply patches with quilt. so all quilt commands should work |
| 12:50.12 | pompomJuice | exactly |
| 12:52.27 | pompomJuice | now that I think of it |
| 12:52.39 | pompomJuice | there might be order issues |
| 12:52.53 | pompomJuice | I have seen people prefix their patches to fix that |
| 12:52.59 | pompomJuice | so rather |
| 12:53.08 | pompomJuice | quilt new 20_foo.patch |
| 12:53.18 | pompomJuice | when your resipy contains 19 patches already |
| 12:53.25 | pompomJuice | and they are all prefixed |
| 12:54.45 | pompomJuice | but that is only neccesary when you patch one file with two different patches somehow |
| 12:55.06 | pompomJuice | so all should be well |
| 12:56.48 | ndec | pompomJuice: patches are not applied based on their filename, but based on the order in SRC_URI |
| 12:57.02 | pompomJuice | aah |
| 12:57.07 | pompomJuice | makes sense |
| 12:57.46 | pompomJuice | and usually new patches go to the tail end |
| 13:00.21 | *** join/#oe bluelightning (~paul@83.217.123.106) |
| 13:00.21 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 13:23.45 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 13:37.13 | *** join/#oe phdeswer (~phdeswer@a88-112-199-213.elisa-laajakaista.fi) |
| 13:49.12 | *** join/#oe blitz00 (~stefans@89.122.246.95) |
| 13:49.28 | *** join/#oe blitz00 (~stefans@unaffiliated/blitz00) |
| 13:50.51 | bencoh | dont we have anything for automatic perl modules deps ? |
| 13:51.00 | bencoh | it's just plain hell as it is :/ |
| 13:51.23 | bencoh | (hello nonetheless :) |
| 14:00.14 | bluelightning | bencoh: right, it's a known problem... we've discussed fixing it over the years but nobody has had time to dig into it beyond that |
| 14:00.47 | bencoh | I guess nobody ever tried to include datetime-format-iso8601 :D |
| 14:02.17 | *** join/#oe nashwhat_ (~nashwhat@2.122.11.119) |
| 14:27.23 | *** join/#oe WarheadsSE (~WarheadsS@50.164.115.22) |
| 14:31.03 | *** join/#oe RushPL (~quassel@dragon.rushbase.net) |
| 14:48.31 | WarheadsSE | Hey all. Having trouble locating the problem: kernel modules aren't getting stripped. (Dora) |
| 14:59.13 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 15:01.38 | JaMa | anyone knows why bitbake still selects libav as libpostproc provider (instead of separate recipe)? |
| 15:01.41 | JaMa | NOTE: preferred version 9.13 of libav not available (for item libpostproc) |
| 15:01.43 | JaMa | NOTE: versions of libav available: 0.8.11 |
| 15:02.07 | JaMa | building just libpostproc selects right provider |
| 15:02.21 | JaMa | but DEPENDS from some other recipe still selects libav |
| 15:06.52 | ant_work | JaMa: see comments in e8f9420 |
| 15:08.23 | ant_work | BBL |
| 15:10.18 | JaMa | there is also libpostproc package incorrectly in libav-9 PACKAGES_DYNAMIC http://lists.openembedded.org/pipermail/openembedded-core/2014-July/094404.html |
| 15:10.26 | JaMa | but the warning is still there :/ |
| 15:28.54 | *** join/#oe staylor (~staylor@S010678542efe021b.cg.shawcable.net) |
| 15:45.14 | *** join/#oe awozniak (~awozniak@71-93-61-178.static.snlo.ca.charter.com) |
| 15:52.40 | WarheadsSE | No thoughts on kernel modules not being stripped? |
| 16:16.32 | *** join/#oe Nitin (~nakamble@192.55.54.40) |
| 16:22.35 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 16:22.48 | *** join/#oe Jafura (~Jean-Fran@2a02:2788:114:11ce:bd25:9aed:ec1e:701b) |
| 16:26.14 | ndec | denix: around? i am doing an oe-core + meta-ti build for BBB. noticed that 'kernel' package is not included by default, as such the board doesn't boot with all default generated files. |
| 16:26.23 | ndec | is that really intentional? |
| 16:26.56 | *** join/#oe Gaston|Home (~jonma@ua-83-227-239-139.cust.bredbandsbolaget.se) |
| 16:29.09 | *** join/#oe Gaston|Home (~jonma@ua-83-227-239-139.cust.bredbandsbolaget.se) |
| 16:35.34 | *** part/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 16:35.35 | *** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy) |
| 16:35.38 | nerdboy | moin |
| 16:35.44 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 17:38.52 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
| 17:48.54 | *** join/#oe kuldeepdhaka (~kuldeepdh@unaffiliated/kuldeepdhaka) |
| 17:49.08 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
| 18:15.11 | *** join/#oe biggieshellz (~bshelton@130.164.62.143) |
| 18:18.34 | kergoth | man, tantalizingly close to getting a functional toolchain from my newly restructured meta-sourcery with split-recipes |
| 18:20.20 | beshelto | Quick question: Is it possible to know at build time which version of tar will be used in the image (busybox or GNU)? |
| 18:20.45 | kergoth | depends on what image you're building, and how your busybox is configured |
| 18:21.41 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 18:22.23 | beshelto | The use case is that in udev-cache, I'd like to be able to use the "--exclude=log" option to tar, which exists in GNU tar but not busybox tar |
| 18:23.10 | beshelto | We've broken the tar arguments into a parameter in meta/recipes-core/udev/udev/udev-cache.default like this: |
| 18:23.20 | beshelto | DEVCACHE_EXTRACT_OPTS="--exclude=log -m" |
| 18:23.54 | beshelto | but we'd like the ability not to use the --exclude=log argument if the system tar doesn't support it, and ideally, we'd like to find that out at build time rather than having to check the version in the initscript. |
| 18:31.42 | *** join/#oe challinan (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
| 18:37.07 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
| 18:41.12 | *** join/#oe flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 18:44.08 | *** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian) |
| 18:47.33 | denix | ndec: see item #4 here http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto/tree/README.hardware#n190 |
| 19:05.08 | *** join/#oe dvhart (dvhart@nat/intel/x-twheshvgfbjrgush) |
| 19:11.05 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 19:18.48 | *** join/#oe rob_w (~rob@unaffiliated/rob-w/x-1112029) |
| 19:41.01 | *** join/#oe challinan_ (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
| 19:48.39 | *** join/#oe ant_home (~andrea@host253-222-dynamic.20-79-r.retail.telecomitalia.it) |
| 20:07.39 | *** join/#oe dvhart (~dvhart@134.134.139.76) |
| 20:14.48 | *** join/#oe jackmitch|home (~Thunderbi@cpc22-cmbg15-2-0-cust21.5-4.cable.virginm.net) |
| 20:28.54 | *** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se) |
| 20:36.38 | *** join/#oe challinan (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
| 20:52.38 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 20:58.02 | *** join/#oe Crofton (~balister@rrcs-173-197-103-2.west.biz.rr.com) |
| 21:00.27 | *** join/#oe hbeck (~hbeck@38.114.125.90) |
| 21:04.35 | *** join/#oe woglinde (~henning@f052197221.adsl.alicedsl.de) |
| 21:08.18 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 21:36.08 | *** join/#oe hillct (~hillct@c-71-192-246-150.hsd1.ma.comcast.net) |
| 21:48.37 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
| 21:48.37 | ndec | denix: nice! it was documented properly! i guess this is equivalent to simply add 'kernel' in the image which is what i am doing.. |
| 21:49.38 | denix | ndec: it actually gets into the image automatically. the exception is core-image-minimal, because that doesn't follow the rules... |
| 21:50.15 | ndec | aren't rules meant to be broken? |
| 21:50.39 | *** join/#oe ensc|w (~ensc@fedora/ensc) |
| 21:50.53 | denix | ndec: heh :) |
| 21:54.45 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
| 22:00.38 | *** join/#oe roric (~roric@c-107ae455.213-3-64736c14.cust.bredbandsbolaget.se) |
| 22:09.10 | *** join/#oe challinan (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
| 22:11.20 | *** join/#oe Shawn287 (~Shawn@unaffiliated/shawn156) |
| 22:26.53 | *** join/#oe awozniak (~awozniak@71-93-61-178.static.snlo.ca.charter.com) |
| 22:34.41 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
| 22:49.58 | *** join/#oe jkridner (~jkridner@d14-69-171-23.try.wideopenwest.com) |
| 22:49.58 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
| 22:57.21 | *** join/#oe Nitin (nakamble@nat/intel/x-yrslutxoulijquvw) |
| 22:58.39 | *** join/#oe woglinde (~henning@f052018135.adsl.alicedsl.de) |
| 23:04.14 | *** join/#oe GusBricker (~GusBricke@cre1513898.lnk.telstra.net) |
| 23:22.41 | *** join/#oe hkdnl (~hkdnl@ip3e83f83d.speed.planet.nl) |
| 23:58.01 | *** join/#oe nerdboy (~sarnold@gatekeeper.gentoogeek.org) |