IRC log for #oe on 20070503

00:00.27polyonymousI'll got for a getpagesize().
00:00.44polyonymousI'm afraid there will be too many packages depending on virtual/kernel otherwise :)
00:28.17polyonymouspsokolovsky__, http://bugs.openembedded.org/show_bug.cgi?id=2201
00:32.26*** join/#oe mwester-laptop (n=mwester@nslu2-linux/mwester)
00:45.45*** join/#oe idealm (n=ideal@c58-107-18-60.belrs2.nsw.optusnet.com.au)
00:50.37*** join/#oe vervain__ (n=vervain@74-139-209-151.dhcp.insightbb.com)
01:02.38*** join/#oe Sonic|Laptop (n=Garrett@cblmdm72-240-97-94.buckeyecom.net)
01:07.56*** join/#oe jkilb_ (n=jkilb@p5B20CB8E.dip0.t-ipconnect.de)
01:11.38*** join/#oe wrobbie (n=rob@cm74.kappa84.maxonline.com.sg)
01:13.11*** join/#oe Laibsc1 (n=Laibsch@c-134-230-233.f.dsl.de.ignite.net)
01:48.25*** join/#oe jacques (n=jacques@nslu2-linux/jacques)
01:50.27*** join/#oe greentux (n=lemke@pd956a57b.dip0.t-ipconnect.de)
02:28.03*** join/#oe emte__ (n=emte@d64-180-45-14.bchsia.telus.net)
02:28.36*** join/#oe Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net)
02:31.06xjqian(09:11:03 PM) xjqian: the README in the opie-1.2.3 reads OPIE II, but I though the opie-1.2.3 is just a minorly improved (release frozen) version of opie-1.2.2 (a.k.a opie I)
02:31.06xjqian(09:11:10 PM) xjqian: now I'm confused
02:31.06xjqian(09:14:51 PM) xjqian: the qtopia/qt files in the opie-1.2.3 do look like newly released version from Trolltech. hence it does indicate OPIE II from the perspective it uses new qtopia libraries
02:31.06xjqian(09:16:26 PM) xjqian: so does opie-1.2.3 mean a mixture of new qtopia libraries with old qtopia applications, which implies that most of the application will be broken and need to be rewritten?
02:31.52xjqiansorry, but nobody in the opie channel responded. so I'm trying my luck here
02:44.14*** join/#oe jacques (n=jacques@nslu2-linux/jacques)
02:44.50*** join/#oe jacques (n=jacques@nslu2-linux/jacques)
02:59.59*** join/#oe tank17 (i=ariel@gateway/tor/x-d1d690db0965a7df)
03:00.22xjqiannever mind, I found the answer
03:07.22xjqianNote that this will build packages with version "1.2.2+cvs2007xxxx", which uses the old qtopia or QT/embedded-2.3.10  Note that this is not the OPIE II project (which unfortunately labeled itself opie-1.2.3 after svn checkout):  http://www.linuxtogo.org/gowiki/OpieProject., which uses the new qtopia-4.2.1.  
03:07.31xjqianupdated wiki here: http://www.linuxtogo.org/gowiki/OpieWithAngstrom
03:36.34*** part/#oe mreimer_ (n=mreimer_@luthien.vpop.net)
03:39.13psokolovsky__xjqian: your update reverted, please read the page, or at least intro, before making random changes. thanks.
03:46.46xjqianpsokolovsky: that's fine and yes i've read the intro
03:47.36xjqianpsokolovsky: could you link the opie II page to the intro, so people know which one is which.
03:48.02psokolovsky__xjqian: then it must have been clear taht it's not opie2, as intro makes that pretty unambiguous
03:48.37psokolovsky__xjqian: I will some next time, or you're welcome to do that
03:48.38xjqianpsokolovsky: what seems confusing to me is http://www.linuxtogo.org/gowiki/OpieProject?highlight=%28opie%29 has the title OpieProject
03:50.12psokolovsky__xjqian: this issue was already raised to opie2 organizer. he's response was along the lines that creating confusion among the users would be one of his aims. so, enjoy your flight.
03:50.44psokolovsky__xjqian: there's extensive discussion on opie-devel list if you're interested
03:51.42xjqianugh. i see. another confusion is after svn checkout svn://projects.linuxtogo.org/svn/opie/trunk  opie II creates a directory opie-1.2.3 by default
03:52.06xjqianthanks for the pointer
03:55.08*** join/#oe Marex (n=Marex@85.132.236.161)
03:58.34*** join/#oe jamie (n=jamie@pdpc/supporter/active/jamie)
04:14.44*** join/#oe tank17 (i=ariel@gateway/tor/x-f30ee3c43541ac12)
04:16.51ljpi dont think opieII labeled itself as opie 1.2.3
04:21.45xjqianljp: your're right. sorry my mistake
04:23.24*** part/#oe pierrelux (n=pierre-l@144-125.sh.cgocable.ca)
04:23.26xjqianljp: indeed, interesting reading in the opie mailing list. ljp, I see your point. But I'm on psokolovsky's side for the confusion in naming.
04:24.26ljpwhats the confusion?
04:24.50ljpt would have been confusing if opieII was just opie
04:26.57xjqianthen why not register opie as opieII
04:27.05ljpi never said one of my aims was creating confusion among users, thats just bs
04:27.29ljpthe name IS opieII
04:27.33xjqianand in serveral wiki pages, http://www.linuxtogo.org/gowiki/GettingOpieSources, this for example
04:27.42humsatmorn :)
04:27.52xjqiani was linked to this page from the mailing list
04:28.01ljpquite less confusiong than the whole GPE hubbub
04:28.19xjqianand there's no indication at all this is to fetch opieII
04:28.46xjqiannot a single sign until I got the source and read the README in the trunk
04:29.20xjqiani know it's not your intension to confuse people, but how the wiki pages are written is really confusing
04:32.04xjqianesp to people new to opie
04:32.28ljpok, well. i will clean tham up when i get the chance
04:33.32xjqianthanks
04:34.41psokolovsky__ljp: of course you didn't say that. you said that you don't care, and did it confusing way. so don't be surprised that people start to think that you want the confusion.
04:35.28ljpwell, someone telling them that wont help
04:35.42*** part/#oe _law_ (n=_law_@213.173.86.202)
04:36.17*** join/#oe Gerrath (n=Gerrath_@unaffiliated/gerrath)
04:36.20psokolovsky__ljp: and as for gpe then again, it seems like there's funky inclination to follow that way. and that strange - while working on opie2, wouldn't it be good idea to keep opie1 users warm and not dissatisified with confusion?
04:37.57ljpi still dont see where any confusion is.
04:38.26ljpi could have committed the code to handhelds.org, but i didnt
04:53.30psokolovsky__ljp: you decide where to host. but if you consistently used opieII/opie2 name everywhere (including project/repo internal names), that would be helpful for people
04:57.10*** join/#oe donato_home (n=donato@c9501fd2.bhz.virtua.com.br)
05:14.59*** join/#oe _law_ (n=law@mail.stiftadmont.at)
05:18.08*** join/#oe goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
06:06.36*** join/#oe Sup3rkiddo (n=sudharsh@59.92.13.37)
06:12.59*** join/#oe Ironnads_ (n=Ironnads@host86-135-183-103.range86-135.btcentralplus.com)
06:13.29*** join/#oe mithro (n=tim@lester.mithis.com)
06:18.52*** join/#oe zecke (n=ich@91.64.161.147)
06:20.46koengood morning all
06:23.41zeckemoin
06:30.48zeckekoen: you pay taxes?
06:31.07koenyes, but since I'm a student, I get it all back
06:31.24koenmy employers pay taxes for me automagically
06:34.59*** join/#oe Sleep_Walker (n=Sleep@195.22.44.103.adsl.nextra.cz)
06:36.57Laibsc1psokolovsky__: qemu-native compilation with the patch finished fine.
06:37.30LaibschGood morning
06:37.36psokolovsky__morning!
06:37.55psokolovsky__Laibsch: cool, now just tell us that it aslo able to generate working locales ;-D
06:43.05Laibschpsokolovsky__: That is all the testing I was going to do on that one.
06:43.29LaibschI already reversed the patch and cleaned out that qemu-native
06:43.44LaibschThe working locale part is left up to you ;-)
06:44.26Laibschpsokolovsky__: I interrupted the bitbake clean
06:44.37LaibschHow do I find out if it generates working locales?
06:44.40psokolovsky__lol. as if somebody doubted it does compile ;-)
06:44.51Laibschpsokolovsky__: I thought you did
06:45.00LaibschI at least was not sure.
06:45.14LaibschIf that does not help, then fine
06:45.22LaibschNot my problem
06:45.29psokolovsky__Laibsch: first step is apparently try to build locale(s) at all. if it won't segfault, good sign
06:45.35LaibschI got a solution I deem superior for me
06:45.59Laibschpsokolovsky__: "bitbake glibc" ?
06:46.06psokolovsky__Laibsch: then, you can just save generated packages and compare with gcc3-compiled-qemu later (or uplaod so someone else did that)
06:46.16LaibschI am sorry but I don't  have the time for that
06:46.19psokolovsky__Laibsch: yep
06:46.34LaibschNah, you will have to do that.
06:46.38psokolovsky__Laibsch: but you'd need to do anyway, right?
06:46.46psokolovsky__ok
06:47.22Laibschpsokolovsky__: I do *not* want anything compiled that I will use later on while this untested patch is applied
06:47.22psokolovsky__my whole idea of asking you was that you do a clean rebuild on a new machine, and could follow thru all that
06:47.30psokolovsky__ok
06:47.39Laibschpsokolovsky__: That takes me several days as you know
06:47.47Laibschan image might even take a week
06:47.57LaibschI am not cleaning out tmp to test a single bug
06:49.08psokolovsky__Laibsch: with GLIBC_GENERATE_LOCALES locale generation alone takes 10mins max, add ~1-2hr compiling glibc
06:49.22Laibschnot my machine
06:49.28Laibschnot on my bb machine
06:49.40psokolovsky__ok, sorry to bother you then ;-)
06:49.45LaibschAnd I don't even want to spend ~1-2 hours
06:49.51Laibschnp
06:49.55zeckelater
06:50.12Laibschzecke: Still up?  Later
06:50.26LaibschSeems like everybody skipped sleeping last night
06:52.42CIA-403koen 07org.oe.dev * rf93b1c50... 10/ (1 packages/cairo/cairo_git.bb): cairo-git: update PV
07:04.47*** join/#oe dhr (n=hugh@CPE00606767ed59-CM000f9fa81660.cpe.net.cable.rogers.com)
07:14.57*** join/#oe Laibsch (n=Laibsch@c-134-230-233.f.dsl.de.ignite.net)
07:18.32*** join/#oe likewise (n=chatzill@atwork-186.r-212.178.104.atwork.nl)
07:18.46likewisehello all
07:19.13koenhey likewise
07:19.25likewisehey koen
07:19.42koenlikewise: http://ewi546.ewi.utwente.nl/tmp/eabi-eb.diff
07:20.43likewisekoen: yup, something like that should do it (finger crossed still)
07:21.12likewisekoen: haven't been able to test yet, my nightly build was broken
07:22.07koenI have a toolchain now
07:23.21likewiseI'm still having problems that every package and then some gets pulled in my images... at least in the build
07:28.10koenyou can avoid that by giving each task-* in task-base.bb its own recipe
07:29.57CIA-403polyonymous 07org.oe.dev * rb896e366... 10/ (6 files in 3 dirs):
07:29.57CIA-4qte, qte-mt 2.3.10: Fix build with recent kernel headers.
07:29.58CIA-4* Closes #2201.
07:30.01CIA-403pfalcon 07org.oe.dev * ra2852adc... 10/ (4 files in 3 dirs):
07:30.01CIA-4opie-todo cvs: Unbreak system-wide logging.
07:30.01CIA-4* A specific app may not override system-wide parameter on a whim - it's
07:30.01CIA-4under user control.
07:30.07CIA-403pfalcon 07org.oe.dev * r388abcdc... 10/ (3 files in 3 dirs): (log message trimmed)
07:30.07CIA-4opie-taskbar cvs: Don't bother to start qss from C++ code.
07:30.08CIA-4* Because it's useless - to have a separate process for sound server,
07:30.10CIA-4and then have mishacks to start/keep alive it hardcoded in C++. That doesn't
07:30.12CIA-4work somehow (h4000, hx4700, etc. machines have issues), and then it
07:30.14CIA-4completely non-debuggable.
07:30.16CIA-4* So instead, qss should be started separately, of course from a shell script.
07:30.18CIA-403pfalcon 07org.oe.dev * r686b8a7b... 10/ (1 packages/tasks/task-opie.bb):
07:30.20CIA-4task-opie: Add opie-qss, an OPIE sound server, essential component.
07:30.22CIA-4* Fixed #2211.
07:30.26CIA-403pfalcon 07org.oe.dev * rc3d8d21c... 10/ (3 files in 3 dirs):
07:30.28CIA-4opie-init: Start qss daemon.
07:30.30CIA-4* Fixes #2211.
07:30.32CIA-403pfalcon 07org.oe.dev * rdb859e25... 10/ (1 packages/opie-init/opie-init/opie): opie-init: Actually daemonize qss.
07:30.37CIA-403koen 07org.oe.dev * r4bc8cc04... 10/ (4 files in 3 dirs): gcc 4.1.2: fix 800-arm-bigendian.patch
07:40.33koenlikewise: updated patch is in
07:45.32likewisekoen: starting a fresh build then for ixp4xxbe/angstrom
07:48.00*** join/#oe zecke (n=ich@dsl-62-220-14-162.berlikomm.net)
07:49.47likewisezecke: good morning
07:50.10*** join/#oe greentux (n=lemke@ip-217-18-181-130.static.reverse.dsi.net)
07:50.31zeckemoin
07:50.35zeckeLaibsch: now I'm here
07:52.50koenyou're not here, you're in berlin
07:54.24*** join/#oe rd_ (n=rd@vnsecurity.net)
07:57.47zeckekoen: what makes you believe that?
07:58.01koenyour sith powers
08:05.07zecke;)
08:05.12zecke~snack for koen
08:05.21ibotACTION throws for koen a doggy treat
08:07.47*** join/#oe obergix[work] (n=olivier@inf-berger.int-evry.fr)
08:16.34CIA-403koen 07org.oe.dev * r2b2a9e8b... 10/ (3 files in 3 dirs): linux-ezx 2.6.21: update to r1996, fixes some oopses
08:20.33*** join/#oe univac (n=univac@suita.chopin.edu.pl)
08:35.39*** join/#oe univac (n=univac@suita.chopin.edu.pl)
08:39.09*** join/#oe univac (n=univac@suita.chopin.edu.pl)
08:39.27*** join/#oe pH5 (n=ph5@e178202105.adsl.alicedsl.de)
08:43.14*** join/#oe zecke (n=ich@dsl-62-220-14-162.berlikomm.net)
09:00.03*** join/#oe lrg (n=liam@lrg2.demon.co.uk)
09:12.25*** join/#oe univac (n=univac@148.81.191.193)
09:20.13*** join/#oe polyonymous_ (n=hacker@pD953907D.dip0.t-ipconnect.de)
09:33.44*** join/#oe Kristoffer|afk (n=Kristoff@81-233-95-80-no75.business.telia.com)
09:42.52*** join/#oe z72ka-ntb (n=hermanj@tux2.software602.cz)
09:42.58*** join/#oe ade|desk (n=adavey@194.200.143.249)
09:43.52*** join/#oe woglinde (n=heinold@leningrad.mi.fu-berlin.de)
09:43.53ade|deskmonring
09:43.56*** join/#oe emte (n=emte@d64-180-45-14.bchsia.telus.net)
09:54.30*** join/#oe goxboxlive (n=goxboxli@195.159.97.196)
09:54.48*** join/#oe pleemans (n=peter@d5152D19B.access.telenet.be)
09:54.54woglindehi ade
09:58.33*** join/#oe florian (n=fuchs@217.146.132.69)
10:06.05polyonymousmood gorning.
10:06.28woglindehi polyonymous
10:06.37polyonymoushi.
10:07.58polyonymousLaibsch, I wouldn't say that 'opie in angstrom' metabug depends on the dual gpe/opie image bug ;-)
10:10.41LaibschMy interpretation as creator of the meta-bug is "all bugs related straight to opie"  which is true.
10:12.57Laibschto rephrase it, koen should be able to safely ignore any bug that is blocking it ;-)
10:14.21likewiseCould this be a dash/bash issue? | make[3]: Leaving directory `/home/leon/sandbox/ixp4xxbe-eabi/openembedded/build/tmp/work/x86_64-linux/perl-native-5.8.7-r5/perl-5.8.7/x2p'
10:14.23likewise| ../makedepend: 1: Syntax error: Unterminated quoted string
10:14.45koenlikewise: probably
10:14.49zeckelikewise: yes, makedepend of perl is broken :)
10:14.54koenI built 5.8.8, which is dash-safe
10:15.13polyonymousLaibsch, I just stated my opinion, I'm not feeling like fighting for it :)
10:15.15likewiseok, tnx.
10:15.22Ifaistosmorning all
10:15.34likewisemorning Ifaistos
10:15.47likewise***good*** morning Ifaistos
10:16.20koenlikewise: http://www.openembedded.org/~koen/ARM-eb-EABI-rootfs.tgz
10:21.08likewisekoen: got it. need to prep some h/w setup here.
10:22.41likewisehmm. no. need to build an EABI kernel first
10:22.48polyonymousLaibsch, tried to hack around your collie psplash (bug 2149), yet?
10:33.32polyonymousopie-todo doesn't build, hmm...
10:39.03koenlikewise: Lennert: Yep, werkt perfect.  Dus toch __ARMEB__-issues..
10:46.23psokolovsky__Hi!
10:46.40polyonymoushey
10:46.47psokolovsky__koen: So, can you link http://linuxtogo.org/gowiki/AngstromFaq for word "FAQ" on angstrom site?
10:46.55*** join/#oe rd__ (n=rd@toi.yeu.phu.nu)
10:47.22psokolovsky__koen: or do you leave that as an exercize to a reader - read wiki and discover faq?
10:47.36*** part/#oe rd__ (n=rd@toi.yeu.phu.nu)
10:47.37psokolovsky__koen: please don't, *many* people will fail it ;-)
10:47.43polyonymousif ti was hard to write it should be hard to understand :)
10:48.11psokolovsky__koen: and thanks and congrats on the facelift of the site ;-)
10:56.37likewisekoen: what works perfectly? your rootfs?
10:56.48koenlikewise: yes
10:57.07likewisekoen: ok, so the missing patch hunk was the root of all evil?
10:57.18koenlikewise: it seems that way
11:00.19*** join/#oe Sleep_Walker (n=Sleep@195.22.44.103.adsl.nextra.cz)
11:03.50*** join/#oe rd_ (n=rd@toi.yeu.phu.nu)
11:12.27chouimatmorning
11:12.33koenhey chouimat
11:13.42*** join/#oe woglinde (n=heinold@leningrad.mi.fu-berlin.de)
11:33.25xjqianpsokolovsky__: bitbake -c clean only cleans up stuff in tmp/work. Are there any other bitbake -c command that cleans up stuff in tmp/staging (or I have to clean those manually). (I've read the bb manual and can't find any enlightenment, btw)
11:34.19*** join/#oe blayne (n=blayne@dsl093-039-078.pdx1.dsl.speakeasy.net)
11:37.44*** join/#oe Marex (n=Marex@85.132.236.161)
11:45.58psokolovsky__xjqian: no. finish "packaged staging" thing if you want it ;-)
11:46.42*** join/#oe grma (n=grma@85-126-107-146.static.sdsl-line.inode.at)
11:46.45*** join/#oe grma_ (n=grma@85-126-107-146.static.sdsl-line.inode.at)
11:46.55xjqianpsokolovsky__: got it. thanks
11:47.04koenpsokolovsky__: expect some updates to packaged-staging during GUADEC :)
11:47.17psokolovsky__koen: cool!
11:47.53*** join/#oe grma (n=grma@85-126-107-146.static.sdsl-line.inode.at)
11:48.58*** join/#oe idealm (n=ideal@c58-107-18-60.belrs2.nsw.optusnet.com.au)
11:49.06polyonymouspsokolovsky__, just FYI - on my Z sound in opie works on initial start as well.
11:49.33psokolovsky__polyonymous: since when?
11:50.38polyonymouspsokolovsky__, don't know, I've just tested with a fresh image.
11:50.38polyonymousthe one that doesn't build (2224:)).
12:06.47koenRP: the install patch works fine, the only exception being do_deploy
12:07.44polyonymouspsokolovsky__, regarding 2224 - I think the patch was older than your recent cvs bump?
12:08.54psokolovsky__polyonymous: no. please describe the exact issue you have, not ideas what it might be
12:09.16polyonymouspsokolovsky__, what is there to describe? The patch doesn't apply, because it's already there after checkout.
12:09.29likewiseNOTE: <type 'exceptions.TypeError'>:argument of type 'NoneType' is not iterable while evaluating:
12:09.31likewise${@['armv5teb', 'armv5te'][bb.data.getVar('SITEINFO_ENDIANESS', d, 1) == 'le']}
12:10.00psokolovsky__polyonymous: link to upstream please
12:10.20*** join/#oe mithro (n=tim@ppp246-117.static.internode.on.net)
12:11.08*** join/#oe svolpe_gerrath (n=Gerrath_@unaffiliated/gerrath)
12:11.17*** join/#oe hwtechnik (n=hwtechni@f1.globalcore.net)
12:11.39*** join/#oe benlau (n=benlau@221.125.13.148)
12:12.41polyonymouspsokolovsky__, heck, it's two years old, but it DOES contain the patch: http://handhelds.org/cgi-bin/cvsweb.cgi/opie/core/pim/todo/main.cpp?rev=1.11&content-type=text/x-cvsweb-markup
12:13.32polyonymoushmm..
12:13.34likewisekoen: Now this can be reversed I guess?  http://www.openembedded.org/viewmtn/revision.psp?id=f342c01c457224ae016d92fea9fbf40b24d88f32
12:13.35psokolovsky__polyonymous: ok, let's start from the start. which patch?
12:13.49koenlikewise: yes
12:13.55polyonymouspsokolovsky__, hang o.
12:13.55polyonymousn
12:14.11*** join/#oe nm (n=hongtd@222.252.102.104)
12:14.52polyonymouspsokolovsky__, forget it.
12:15.05CIA-403pfalcon 07org.oe.dev * re51f8fd8... 10/ (3 files in 3 dirs):
12:15.05CIA-4libqpe-opie cvs: Unbreak logging.
12:15.05CIA-4* Again, it's bad idea to randomly disable some logging sources based on
12:15.05CIA-4obscure compile-time defines (QT_DEBUG is not mentioned in qte-2.3.10, so
12:15.05CIA-4how could it get such name at all?). OE OPIE is going to have logging facility
12:15.05CIA-4helping to resolve issues, not obfuscate them.
12:16.02CIA-403koen 07org.oe.dev * ra8e33b18... 10/ (1 conf/machine/ixp4xxbe.conf): ixp4xxbe: the gcc patch is in, so no need for this workaround anymore
12:17.19koenlikewise: there you go
12:17.42polyonymouspsokolovsky__, not exactly forget it - the patch doesn't apply. I don't know what I was looking at, when I said it doesn't apply, because it's already there.
12:18.15likewisekoen: and http://www.openembedded.org/viewmtn/revision.psp?id=bc8cfed5e37f251070c62f9cef49b1db7aa86264
12:18.32psokolovsky__polyonymous: yes, that's true. reasons not true. first rule of system enginering - don't trust anything, verify ;-)
12:18.58polyonymouspsokolovsky__, Yes, I do not have much to say in my defense :)
12:19.22psokolovsky__and now I wonder who on earth was such smart as to stuff some gnome crap for patch conflict resolution?!
12:19.26koenlikewise: right
12:19.27polyonymouspsokolovsky__, it's todo/ path, have you fixed it yet?
12:19.41psokolovsky__shame, shame! people forgot what unix is! they use some
12:20.03psokolovsky__"leenooks" crap with dwarfs and stuff, instead of commandline!
12:20.05psokolovsky__shame!
12:21.15psokolovsky__# Set a default
12:21.15psokolovsky__TERMCMD ?= "${GNOME_TERMCMD}"
12:21.17psokolovsky__b/s
12:21.27polyonymouspsokolovsky__, I'm running away now. I don't know if you fixed that patch, just in case: http://rafb.net/p/khF9fi12.html
12:22.20likewisekoen: thanks.
12:22.37koenlikewise: could you revert the patch, I'm about to run off
12:22.44likewiseI am hitting a bitbake problem here or something else? http://www.pastebin.ca/468837
12:22.56likewisekoen: yes, will do
12:23.03likewisekoen: cu
12:23.13koenlikewise: no TARGET_OS?
12:24.12koen(armeb-INVALID vs armeb-linux)
12:24.12likewisekoen: using MACHINE=ixp4xxbe with DISTRO=angstrom-2007.1
12:24.12likewisekoen: lemme check eb vs be
12:25.06likewisekoen: ixp4xxbe
12:31.19*** join/#oe z72ka-ntb (n=hermanj@tux2.software602.cz)
12:33.13*** join/#oe marcan (n=marcanso@160.10.7.121)
12:48.28CIA-403lenehan 07org.oe.documentation * ref06b87a... 10/ (1 usermanual/reference/image_types.xml): (log message trimmed)
12:48.28CIA-4usermanual: Update image types to match recent changes:
12:48.28CIA-4- ext3 and ext3.gz have been added
12:48.28CIA-4- cpio and cpio.gz have been added
12:48.28CIA-4- default options for jffs2, squashfs and squashfs-lzma have been changed
12:48.29CIA-4- ext2.gz now deletes tmp files so leftovers don't break next run
12:48.31CIA-4- tar has been changed to make tars instead of tar.bz2's
12:48.41*** join/#oe rd_ (n=rd@toi.yeu.phu.nu)
12:49.34*** join/#oe grma (n=grma@85-126-107-146.static.sdsl-line.inode.at)
13:08.07RPpsokolovsky__: What is your problem?
13:10.35psokolovsky__RP: Well, mail should describe it well enough - no rc check for "terminal" command, out-of-hand default for such command. I leave interpretation of the rest to you ;-)
13:11.12RPpsokolovsky__: You just succeeded in massively pissing me off...
13:12.08psokolovsky__RP: I'm sorry, but I tried to make it both funny and "cognitive"
13:12.38psokolovsky__RP: it's also pissing off for me to understand that I could been building broken images for a month now %)
13:13.31*** join/#oe daurnimator (i=daurn@unaffiliated/daurnimator)
13:13.38RPpsokolovsky__: I can understand that being frustrating. We are all trying to develop various things and with the best will in the world, things do break though
13:14.34ade|deskhmm OT: can you break broken glass ?
13:15.55psokolovsky__RP: yeah, but I clear added humoresque shade to that "report", no? maybe just too "vivid", because I'm not sure I could argue to success that such a tool like bitbake should *not* depend on nay GUI stuff ;-I
13:16.40psokolovsky__RP: otherwise, I of course didn't intend to make you frown in a day ;-)
13:17.10polyonymousIt's my fault, I made psokolovsky__ mad today :)
13:17.20polyonymousprobably, he passed the piss :)
13:18.08psokolovsky__polyonymous: well nope, but I wonder if you had the same issue. I initially thought you did
13:18.20polyonymouspsokolovsky__, the same like what?
13:18.49polyonymouspsokolovsky__, I indeed goofed twice today.
13:19.02psokolovsky__polyonymous: like silent failure to patch, though I now guess it wasn't your case
13:19.11*** join/#oe TheCan (n=thecan@dslb-084-056-185-005.pools.arcor-ip.net)
13:19.31polyonymouspsokolovsky__, maybe it's just my setup, but it wasn't quite failure. It was quite audible.
13:19.50polyonymouspsokolovsky__, but..
13:19.54RPpsokolovsky__: I've replied to the mail with some hints
13:20.02polyonymousahhh now I know what this GUI stuff you're talking about.
13:20.11polyonymouspsokolovsky__, yes, I've had terminal popup.
13:20.13RPpsokolovsky__: automated builds are why we shouldn't depends on GUI functionality
13:20.27RPpsokolovsky__: but that doesn't mean we shouldn't have optional GUI functionality
13:21.18polyonymousRP, If I get it right, the problem is that it's not optional enough. The rest is emotional miscommunication :)
13:22.09RPpolyonymous: See the reply, it is optional, you just need to know how to configure it. There sounds to be some kind of error propagation bug somewhere too
13:22.11psokolovsky__RP: optional, sure! (especially if you need it). but the change goes towards requiring GUI by default, and I couldn't appreciate that, and I'm sure there're few people around who would agree.
13:22.39polyonymousI haven't even read original mail :)
13:22.52RPpsokolovsky__: Its just a bad default for PATCH_RESOLVER. FWIW, I didn't set that default
13:23.15RPpsokolovsky__: If we want to change it to noop, I'm fine with that
13:23.36polyonymousBut without looking at it (I will in half a minute) I think the solution is comething along the lines `${TERM} || ${BASH}`.
13:23.37RPI do want to find the underlying bug though as command failures should abort the build
13:24.18RPpolyonymous: No, that breaks under multithreading. I've given this a lot of thought and there have been several mails to the mailing list about it
13:24.21psokolovsky__RP: apparently, that's what should be done, right. thanks for proposing that.
13:24.55polyonymousRP, yes, that makes sense, indeed.... then, maybe `|| ${FAIL}`.
13:24.57RPpsokolovsky__: I want to find that underlying bug though - don't just take the simple solution ;-)
13:25.41psokolovsky__RP: yeah, I guess
13:25.52polyonymouswell, anyway. I think you can do without my intervening :)
13:26.01psokolovsky__RP: I will try to do that too a bit later, if you won't beat me on that
13:26.32RPpsokolovsky__: I have other things to do atm. It'll probably be the weekend before I can think about it
13:26.42*** join/#oe mr_nice (n=mr_nice@p54a9fb9f.dip.t-dialin.net)
13:26.58mr_nicehi all
13:27.17polyonymouspsokolovsky__, do I reopen todo bug, or is it not necessary?
13:27.39psokolovsky__RP: ok. again, sorry, if I pulled you from important thing and added unneeded headache. wasn't intended.
13:27.48woglindehi mr_nice
13:27.56mr_nicehi woglinde
13:28.02psokolovsky__polyonymous: I committed it, feel free to try buidl again
13:28.22polyonymouspsokolovsky__, ok. on last pull I've had multihead hydra :)
13:29.28polyonymouspsokolovsky__, And I've just tested the getpagesize() fix - seems to work fine.
13:30.34psokolovsky__polyonymous: nice. I'll commit as soon as I'll do next code session ;-)
13:30.58polyonymousgood. just letting you know, not hurrying you up :)
13:31.31*** join/#oe grma (n=grma@85-126-107-146.static.sdsl-line.inode.at)
13:47.13*** join/#oe mr (n=mr_nice@p54A9FF6C.dip.t-dialin.net)
14:14.32likewiseAarrgh. qemu: uncaught target signal 11 (Segmentation fault) - exiting (this is natively installed qemu on Feisty 7.04)
14:16.32*** join/#oe Sup3rkiddo (n=sudharsh@59.92.93.226)
14:28.26*** join/#oe CosmicPenguin (i=nobody@nat/amd/x-3d1d0f014f7ea603)
14:30.08*** join/#oe z72ka-ntb (n=hermanj@tux2.software602.cz)
14:30.08*** join/#oe vervain (n=vervain@mail.somat.com)
14:45.36*** join/#oe aoe (n=aoe@tigerente.htu.tuwien.ac.at)
14:49.31*** join/#oe jipi (n=jipi@cm128.delta240.maxonline.com.sg)
14:53.01*** join/#oe _law_ (n=_law_@213.173.86.202)
14:55.07*** join/#oe benlau (n=benlau@221.125.13.148)
14:57.45*** join/#oe rd_ (n=rd@toi.yeu.phu.nu)
15:13.32*** join/#oe punkass (n=user@unaffiliated/punkass)
15:16.11*** join/#oe emte (n=emte@d64-180-45-14.bchsia.telus.net)
15:27.22*** join/#oe koen (n=koen@dominion.kabel.utwente.nl)
15:44.22*** join/#oe tnb (n=tnb@sdgsystems.net)
15:50.03*** join/#oe den-ros (n=den@ppp85-140-69-227.pppoe.mtu-net.ru)
15:51.51*** join/#oe zap (n=zap@16.170.249.ozerki.net)
15:53.00*** join/#oe ozstinger (n=ozstinge@216.143.234.167)
16:00.22*** join/#oe goxboxlive (n=goxboxli@176.84-48-210.nextgentel.com)
16:04.32*** join/#oe hvontres|poodle (n=hvontres@68.120.74.196)
16:10.49hvontres|poodlepolyonymous: morinng :)
16:15.48*** join/#oe TheCan (n=thecan@dslb-084-056-185-005.pools.arcor-ip.net)
16:18.58*** join/#oe HopsNBarley (n=hops@nslu2-linux/HopsNBarley)
16:21.03polyonymoushvontres|poodle, yes :)
16:23.06polyonymoushvontres|poodle, got /msg?
16:28.27hvontres|poodlepolyonymous: got it, thanks :) I'll grab it when I get home tonight
16:29.03polyonymousGood. It will be there waiting for you :)
16:39.04*** join/#oe greentux (n=lemke@Z5a36.z.pppool.de)
16:42.45*** join/#oe svolpe (n=Gerrath_@unaffiliated/gerrath)
16:47.04*** join/#oe florian (n=fuchs@217.146.132.69)
17:00.46*** join/#oe vervain (n=vervain@mail.somat.com)
17:14.32*** join/#oe dalurka_ (n=dalurka@holly.bsnet.se)
17:17.59*** join/#oe pleemans (n=peter@d51A5E76A.access.telenet.be)
17:41.36*** join/#oe likewise (n=Leon_Woe@82-171-189-134.dsl.ip.tiscali.nl)
17:42.10*** join/#oe mr_nice (n=mr_nice@p54A9FF6C.dip.t-dialin.net)
17:43.39HopsNBarleyhi likewise!
17:52.27IfaistosCan anyone suggest the best method of creating a single file image with kernel+jffs2 as rootfs with u-boot ?
17:52.28*** join/#oe xuumbi (n=jim@70.90.111.225)
17:52.52Ifaistospaste the files together with dd or use mkimag -T multi option ?
17:56.16*** join/#oe lfn (n=fredric_@130.216.171.66.subscriber.vzavenue.net)
17:58.21*** join/#oe jott (n=j@unaffiliated/jott)
18:03.58likewiseHopsNBarley: hi!
18:04.01likewisehi all
18:04.07NAiLhi likewise
18:04.23likewisekoen: did not commit the revert yet, I didn't have my key with me...
18:04.41koenand I'm playing with a new toy :)
18:05.24likewisekoen: the cam you saw on ebay or something else?
18:05.44likewisekoen: but will commit in a moment.
18:05.46NAiLkoen: what toy?
18:06.08koennew image stabilised lens
18:06.19NAiLah
18:06.24NAiLnot my kind of toy then ;)
18:06.30koendoens't run linux :)
18:06.43NAiLnope
18:06.46NAiLshame ;)
18:08.19likewisekoen: what's the best way to commit? disapprove or just a reverse patch?
18:08.47koenremove the patch from SRC_URI and mtn rm -e it
18:09.19koenDaggyFixes would involve disapproving it and merging, but that makes my brain hurt
18:10.19koenhttp://www.venge.net/mtn-wiki/DaggyFixes
18:10.33*** join/#oe mmp (n=mmp@TheWide.ubyt.sdjls.uniba.sk)
18:12.07lfni have a question about building packages that are subsets of other packages
18:12.40lfnfor example, if i tried creating a diffutils-minimal that only included diff and cmp (omitting sdiff and diff3)
18:13.28lfnhowever, when i build my final image, diffutils is added to it to 'satisfy runtime diffutils-minimal'
18:13.54lfnany thoughts on what i need to do to break this dependence?
18:18.56CIA-403likewise 07org.oe.dev * rd8cede68... 10/ (4 files in 4 dirs): glibc: Remove armeb strlen workaround. We now have the GCC PR16350 patch, take 3 in GCC.
18:28.04*** join/#oe timtimred (n=On3@62-31-181-7.cable.ubr02.chel.blueyonder.co.uk)
18:28.16*** join/#oe gremlin[it] (n=gremlin@217.202.67.189)
18:32.46polyonymouspsokolovsky__, ping?
18:32.56psokolovsky__polyonymous: pong
18:33.09polyonymouspsokolovsky__, why no-builtin-qss-startup.patch ?
18:33.53psokolovsky__polyonymous: read commit message
18:34.00polyonymouspsokolovsky__, good point :))
18:34.01polyonymoussorry
18:34.37psokolovsky__polyonymous: btw, possible, it in fact will be reverted, but instead shell wrapper will be called
18:35.12psokolovsky__polyonymous: of course, unless you have better ideas: a) why pocketpc/palms don't work; b) how to make it all more debuggable
18:35.47polyonymouspsokolovsky__, hmm... when it started autmatically there's no way to kill it and restart elsewhere?
18:35.48*** join/#oe Crofton (n=balister@hc65216ca.dhcp.vt.edu)
18:36.13*** join/#oe emte (n=emte@d64-180-45-14.bchsia.telus.net)
18:36.25polyonymouspsokolovsky__, I'd be glad to find out why pocketpc/palms don't work, but I do not have it :)
18:36.44psokolovsky__polyonymous: no. it stupidly keeps restarting its own instance. that's exactly why that patch - better control by externalizing
18:37.06koenrwhitby: EABI/BE is working now
18:37.11polyonymouspsokolovsky__, I see... The thing is that this 'sleep 1' isn't always enough.
18:38.20psokolovsky__polyonymous: yep, I guess ;-). how much?
18:38.47polyonymouspsokolovsky__, I haven't tried to find out, it depends on device. _sometimes_ sleep 1 _is_enough..
18:39.39polyonymouspsokolovsky__, as for debugging you can rename file for debugging.
18:39.52psokolovsky__polyonymous: again, why I think that maybe calling it from qpe would be better after all - it *knows* when to start it ;-)
18:40.15psokolovsky__polyonymous: no, there're should decend diagnostics means w/o any hacks
18:40.24psokolovsky__should be
18:40.26polyonymousthat's basically the only reason why I raised the issue :)
18:40.41polyonymouswell, debugging _is_ hacking, anyway :)
18:41.24polyonymousI'd that that externalizing for debugging isn't the reason, because debugging is not the primary purpose of running software :)
18:42.17polyonymousSo, I'd rather run it from qpe... But naturally, the issues should be solved...
18:42.30psokolovsky__polyonymous: that's why I call it "diagnostics" after all. Diagnostic support *is* important feature of any complex system.
18:42.57polyonymouspsokolovsky__, "diagnostics" as in "logging" should work from qpe, no?
18:43.08psokolovsky__polyonymous: try it ;-)
18:43.20polyonymouspsokolovsky__, If you say no, I'd believe you :)
18:43.31psokolovsky__and compare with decent solution, like log4j ;-)
18:44.11psokolovsky__polyonymous: it's adhoc, inconsistent, and fragmented. was scarse at all w/o my recent patches
18:45.05polyonymouspsokolovsky__, well, I'm not going to defend this thing, it's just that I doubt the solution is good.
18:45.30psokolovsky__polyonymous: which one? external startup of qss?
18:45.47polyonymousyes, I'm only talking about his. I do not propose redoing the whole opie :)
18:47.50polyonymouspsokolovsky__, what about a little compromise: do not restart qss? :)
18:48.28psokolovsky__polyonymous: yep, that's the problem - opie indeed could use cleanup not only in intergration, but in design. external qss startup is of course rigth thing, but given funky deps on other semi-services, it doesn't work good ;-\
18:49.12psokolovsky__polyonymous: dunno. as I say, plan is to run script, and script can bother with such stuff.
18:49.28polyonymousWhat would be in the script?
18:49.41polyonymousI don't understand how would that help.
18:49.57psokolovsky__polyonymous: "qss >log &" ?
18:50.01*** part/#oe den-ros (n=den@ppp85-140-69-227.pppoe.mtu-net.ru)
18:50.01polyonymousah
18:50.28polyonymouspsokolovsky__, well, I think that's not needed in "production".
18:50.55polyonymousI think this kind of debugging stuff can be better achieved by renaming qss and running it externally for debugging purpose.
18:52.01polyonymouspsokolovsky__, and, anyway, I'd propose no-builtin-qss-restart.patch. It will be shorter too :)
18:52.09psokolovsky__polyonymous: see above - "no, there're should decend diagnostics means w/o any hacks"
18:52.30polyonymousThere will be no decent diagnostics means, anyway :)
18:53.06polyonymousand, again, see above - debugging IS hacking and debugging is not the primary goal of development. For us it may be, but not for user :)
18:54.00psokolovsky__polyonymous: didn't I "infect" you with idea and you'd go to move qte adhoc logging from libqpe-opie to libopie2 (where "opie" logging lives)? ;-)
18:54.39psokolovsky__polyonymous: yeah. diagnostics is. so, debugging with renames is out. diagnostics with script is in ;-)
18:55.44polyonymouswell, I do not really see how is it better in production and that is the primary criterion... But it sure is better than what we have now.
18:56.00psokolovsky__polyonymous: and that attitude is mistake of many commercial vendors (withink one well-known OS vendor). But we don't build terminators here. We'd known there's something wrong long before they will decide to conquere the Earth ;-)
18:56.25polyonymouswhat attitude?
18:57.02psokolovsky__"not part of production"
18:57.45polyonymouspsokolovsky__, wait, what about autostarting qss with -nodaemon?
18:58.31polyonymousWell, I somewhat agree with you on this one.
18:58.36psokolovsky__polyonymous: autostarting where? and I answered - qss.sh
18:58.49polyonymouspsokolovsky__, nah, in opie-taskbar.
18:58.53polyonymousqpe that is.
18:59.29psokolovsky__polyonymous: yes, current idea is to make opie-taskbar run qss.sh. sounds good?
18:59.59polyonymouspsokolovsky__, sounds acceptable. But I was thinking about adding it to qpe, instead of wrapper script.
19:01.01psokolovsky__polyonymous: bit it was in qpe, undiagnostable. I offered you - tell me what's wrong with it on pocketpcs/palms. have answer?
19:01.45*** join/#oe Timelord (n=TL@16.8c.d12c.cidr.airmail.net)
19:02.04polyonymouspsokolovsky__, you know already I have no pocketpcs/palms. Well... why is undiagnostable? Where does the output go when run in qpe?
19:03.45psokolovsky__polyonymous: /dev/null? and important thing from which legs of thsi stuff grow - we must make it such, that we - and not only we - could be able to diagnoze it w/o access to devices.
19:04.34polyonymouspsokolovsky__, who redirects it to /dev/null? You mean it goes there even if qpe is run with -nodaemon?
19:05.31psokolovsky__polyonymous: it goes "somewhere", where you can't find it. didn't I mentioned "adhoc, inconsistent, and fragmented; was scarse" logging?
19:05.54polyonymousWhat about solving exactly this problem?
19:06.32psokolovsky__polyonymous: and at this I already joked and hinted ;-)
19:06.52polyonymousOkay, I'll play around with it.
19:07.20psokolovsky__polyonymous: it == consistent and centralized means of logging, I hope ;-)
19:07.45polyonymousit == making sure that if you run qpe -nodaemon you get qss messages along with other crap.
19:08.20polyonymousI doubt it produces any output, though...  :)
19:08.36polyonymousFor me it's just silent unless it can't connect top qpe :)
19:08.41polyonymouss/top/to
19:09.46psokolovsky__polyonymous: well, you miss the fact that *that* already was done for me. we need general logging support now, not waste time patchinh here and there. ymmv
19:11.16polyonymouspsokolovsky__, I have nothing against logging as long as it doesn't prevent qss from starting up as a side effect :) Or what are you talking about? If you suggest that I just further develop opie, I don't think I'm ready to go for it :)
19:12.02*** join/#oe Timelord (n=TL@16.8c.d12c.cidr.airmail.net)
19:12.02polyonymousNot unless I see where the whole opie thing goes. So far having my trivial patches sitting there for ages doesn't really encourage further enhancements :)
19:12.32psokolovsky__polyonymous: rejigger logging and clean up machine support are two things which would be required to get OPIE to the decent state. note, I even don't mention unit tests ;-)
19:13.24polyonymouspsokolovsky__, well, you're talking from opie's POV. And from that perspective you're absolutely right. But we're on #oe now :)
19:13.46psokolovsky__polyonymous: I fully agree. But for me - I subscribed to maintain opie in OE, and I want to being able to do that, not waste days of my time on each semi-trivial issue.
19:14.11psokolovsky__polyonymous: nope, I speak exactly from OE perspective ;-)
19:14.54polyonymousfrom OE perspective we want to get opie running on as many devices as possible. Well, the usual thing - world domination :)
19:16.01psokolovsky__aim of OPIE in OE - provide well-ingrated system and easy support for new machines. w/o those 2 thinsg above, it's firefighting, not maintenance
19:16.01slapin_nbhi, all!
19:16.03psokolovsky__slapin_nb: hello, lazyboy!
19:16.03slapin_nbabout that commit access, again...
19:16.05polyonymouspsokolovsky__, yes, but that's in fact opie issue, not oe.
19:16.06slapin_nbpsokolovsky__, btw, I think I finish that thing tomorrow.
19:16.10polyonymousI do not mind enhancing opie if I see where it's headed, of course.
19:16.21psokolovsky__slapin_nb: *What* thing? Let me dream!! ;-D
19:16.43*** part/#oe _law_ (n=_law_@213.173.86.202)
19:16.50slapin_nbpsokolovsky__, m-k applet, do you still remember it? :)
19:17.07slapin_nbpsokolovsky__, or that's irrelevant yet?
19:17.11*** join/#oe law|ibook (n=_law_@213.173.86.202)
19:17.35polyonymousspeaking of commit access... :)
19:17.46slapin_nbpolyonymous, yes?
19:18.01polyonymousslapin_nb, nah, that remark wasn't exactly for you :)
19:18.15polyonymousWhat's with m-k applet, btw?
19:18.20slapin_nbpolyonymous, :(
19:18.23*** join/#oe z72ka (n=hermanj@r5af183.net.upc.cz)
19:18.39polyonymousslapin_nb, I didn't mean to offend you.
19:18.41slapin_nbpolyonymous, that's psokolovsky__ to discuss whole idea
19:18.51polyonymousah ok
19:18.57slapin_nbpsokolovsky__,
19:19.06*** join/#oe psokolovsky (n=psokolov@82.193.98.2)
19:19.13polyonymouswb
19:19.14*** join/#oe zecke (n=ich@91.64.161.147)
19:19.38slapin_nbpsokolovsky,
19:19.42psokolovskythese mips routers do hang sometimes, you know...
19:19.46psokolovsky<psokolovsky__> slapin_nb: yep, I just didn't even try to ping you about it, to not be put down! well, you're cool!
19:20.27*** join/#oe woglinde (i=woglinde@e178091232.adsl.alicedsl.de)
19:20.32slapin_nbpsokolovsky, I got time now, so I'm going to flush my TODO, and this one is near top of it.
19:21.16slapin_nbpsokolovsky, so I ask if it's still needed
19:21.28psokolovskyslapin_nb: cool, thanks. on my side, I only cleaned up my older patches for mb-kbd, and put stuff in hg. what's left is exactly to use results of your applet's work ;-)
19:21.42psokolovskyslapin_nb: absolutely and desperately!!
19:22.15slapin_nbpsokolovsky, ok
19:23.09slapin_nbany commit access possibilities for me, btw? (I mean OE.dev)
19:24.08psokolovskyslapin_nb: well, collect your bug submissions and send list to koen/hrw ;-). I'd be glad to vote for you ;-)
19:24.48polyonymouspsokolovsky, what was the outcome of my voting, if this what you'd call voting, btw? :)
19:25.20psokolovskypolyonymous: I'm not core developer, so have no idea of such questions
19:25.29slapin_nbpsokolovsky, ok, thanks!
19:25.58psokolovskypolyonymous: in your place, I'd waite few days more, and send mail to those folks asking for commit, referncing that oe-devel topic
19:26.12polyonymouspsokolovsky, okay, just wondering. I'm quite content with submitting bugs, but now that I have quite a few some of which are definitely safe to commit, it would make sense.
19:27.08psokolovskypolyonymous: I may only agree. the number of submissions increases, and we need more committers to keep up
19:27.23polyonymouspsokolovsky, They're well aware, as hrw said, "speaking of giving commit access to polyonymous" before proposing the other dev for commit access :) Well, I'm not in a hurry anyway - I'd have to learn mtn better. Now I can live with my knowledge :))
19:28.19xuumbihow does bitbake become aware of new package versions, and recompile when a newer version of a package is available for an image/task?
19:28.21psokolovskypolyonymous: well, just keep in mind, that you should be proactive ;-)
19:28.48polyonymouspsokolovsky, or active at the very least, I know. That's always my problem :)
19:29.01psokolovskyxuumbi: latest available version is used, unless masked/pinned. how? by scanning all versions ;-)
19:29.51psokolovskypolyonymous: well, you're active regarding bugs submissions, now be ready to calmly nag OE maintainers ;-)
19:30.29xuumbipsokolovsky: as an experiment I tried changing "r0" to "r1" in my .bb file, but when rebuilding my image it doesn't see the change and rebuild the package
19:30.52xuumbipsokolovsky: so then I changed the version number of the .bb itself, and that didn't get picked up either :(
19:30.58polyonymouspsokolovsky, I prefer patching to nagging :) before I go for two weeks to Moscow, I don't think I'll be pushing it myself. It would be silly - to get access and immediately get off :)
19:31.12psokolovskyxuumbi: it should - PR's are almost never pinned.
19:31.39xuumbipsokolovsky: ok I'll dig deeper, thanks
19:32.14psokolovskyxuumbi: try to build exactly that recipe as initial measure, not the whole image
19:34.00xuumbipsokolovsky: ah, ok, when bitbak'ing the package itself the new version does get picked up
19:34.28polyonymouspsokolovsky, http://rafb.net/p/P99pJD32.html - what about this then? :)
19:35.03xuumbipsokolovsky: I was looking for an easy way of checking to see if a package had a newer version, then automatically rebuilding it when generating a new image, I guess I'll have to write a script for that...
19:35.10psokolovskypolyonymous: that's kinda cool, real unix way ;-)
19:35.18polyonymouspsokolovsky, worksforme :)
19:35.32polyonymousMaybe it should be limited to some finite amount of iterations
19:35.55polyonymouslike for attempt in 0 1 2 3 4 5 6 7 8 9 a b c d e f ;
19:36.17psokolovskyxuumbi: well, it should work with image too, of course, it's just recipes for images should be done right. use existing gpe-image, opie-image as templates
19:36.38psokolovskypolyonymous: works as in tested?
19:36.51polyonymouspsokolovsky, this is a copy'paste from ssh to Z :)
19:37.11psokolovskynice! please submit patch ;-)
19:37.21polyonymousyup. Will attach it to the sound bug.
19:40.56goxboxliveWhy isent libgcc.so installed in the imegaes anymore? I have to add it manually.
19:41.58polyonymousgoxboxlive, have you had rpath failure on gcc-cross?
19:42.20goxboxliveno
19:42.39goxboxliveshould i? How do i do that?
19:42.50polyonymousgoxboxlive, ah, are you talking about binary images?
19:42.58polyonymousor do you bitbake yourself?
19:43.11goxboxliveYes
19:43.29polyonymousif 'yes' was about binaries, then I have no idea :)
19:43.32goxboxliveI am talking about ansgtrom-images
19:44.00goxboxliveit isent installed in console-image or openmoko-image. Haventtried opie yet .
19:44.09goxboxliveI have started with a fresh image today
19:44.31polyonymousdunno about images. I know what could make me end up without half of gcc in my own build. But I doubt it's in "official" binaries.
19:44.46goxboxliveok
19:45.02polyonymoushmm... haven't tried opie? But there's no opie image available?
19:47.24goxboxliveyes there is
19:47.40goxboxlivebitbake opie-image (voila)
19:47.56polyonymousah, so you DO bake it yourself, not talking about binary images for download.
19:48.19polyonymousgoxboxlive, well, are you absolutely sure you didn't have failure on gcc-cross which you had to restart?
19:48.35goxboxlivehmm that might be yes
19:48.44polyonymousgoxboxlive, then, that's it.
19:48.44goxboxliveshould i rebuild it?
19:48.53polyonymousit will fail again :)
19:49.07goxboxliveso, wath to do then?
19:49.16polyonymousgoxboxlive, I had to comment one 'return False' in insane.bbclass to make it non-fatal.
19:49.41goxboxliveok
19:49.43goxboxlivethx
19:52.15*** join/#oe donato_home (n=donato@201.80.134.122)
19:57.19polyonymouspsokolovsky, I attached the patch, but forgot to checke the 'patch' box. Hope, you won't have me resubmit :)
19:57.47psokolovskypolyonymous: you can edit attachment properties after submit ;-)
19:57.52polyonymousnevermind, it's changable
19:57.56polyonymousyeah, I know.
19:58.09polyonymousI believe at some point it wasn't possible, though :)
19:58.25polyonymousOkay, it's in 2211 now.
19:59.49*** join/#oe Crofton (n=balister@hc65216ca.dhcp.vt.edu)
20:00.32psokolovskythanks!
20:00.41polyonymousyou're welcome :)
20:01.18polyonymousI'm afraid 16 seconds aren't enough, though...
20:02.10likewisegoxboxlive, polyonymous: if insane failed, make sure you rebuild the package from start (first -c clean, then build)
20:02.12polyonymouspsokolovsky, or there's another problem... maybe the socket is left after reboot - don't commit yet.
20:02.29polyonymouslikewise, it won't help, it will fail again :)
20:02.48polyonymouslikewise, unless you torture insane itself, that is.
20:02.48likewiseYes, but not with the return commented out.
20:02.56polyonymousyeah.
20:03.14polyonymousand yes, in this case you'd better -c rebuild it.
20:03.23likewiseAh ok, it will fail again now every time? good.
20:03.38polyonymouslikewise, no, no, only after clean.
20:03.48polyonymousWish it would fail consistently.
20:04.06likewiseMe too, the current approach is not deterministic.
20:04.18polyonymousquite deterministic, but I don't like the determination :)
20:04.23*** join/#oe marciom (n=marcio@200.184.118.132)
20:05.00likewiseif it now fails on a package, and you issue the same bitbake again, will it fail again?
20:05.38polyonymouslikewise, no. That's the determination I don't like.
20:06.18polyonymousI would expect something less predictable from nondeterministic approach that is.
20:06.36*** join/#oe koen (n=koen@dominion.kabel.utwente.nl)
20:07.35likewisepolyonymous: yes, that's the issue I'ld like to fix first. Either never fail (warn only), or fail every time.
20:07.52polyonymouslikewise, I don't think we're in any disagreement here :)
20:08.07likewisepolyonymous: which one would you prefer?
20:08.19*** join/#oe Crofton (n=balister@hc65216ca.dhcp.vt.edu)
20:08.28polyonymouslikewise, I'd prefer gcc-cross fixed :)
20:08.53polyonymouslikewise, if I knew how to do it I'd prefer fail consistently. Since I don't - I prefer warn-only :)
20:08.59likewisegcc-cross is of our least concent, it does not arrive on the target.
20:10.07polyonymouslikewise, partially, it does. And failure to build it prevents the whole thing, anyway.
20:10.56likewisekoen: I desperately need a working config for a buildable ARM EABI BE image :-/ Now perl won't build for me. I wonder if I have some host-deps or something.
20:11.11likewisepolyonymous: Replace if bad_dir_test in line: by if bad_dir in line: will at least pass gcc-cross for the moment.
20:12.07polyonymouslikewise, well, I'm content with warn behaviour I have now, so I'd rather not mess with it and move on to something more productive :)
20:12.12likewisekoen: could you please show me the config that built the uploaded EABI BE image for you?
20:12.21likewisepolyonymous: ok
20:14.09*** join/#oe florian (n=fuchs@84.245.184.207)
20:14.50koenlikewise: remove 'gdb' for debug apps, bitbake angstrom-console-image
20:14.54koens/for/from/
20:15.13koenlikewise: and I removed all !5.8.8 perl versions
20:15.59koen(mkdir packages/obsolete/perl ; mtn add packages/obsolete/perl ; mtn mv -e *5.8.4* *5.8.7* ../obsolete/perl)
20:19.19*** join/#oe pierrelux (n=pierre-l@144-125.sh.cgocable.ca)
20:23.11likewisekoen: ah, that explains a bit. But shouldn't we just be simply able to remove the dependency on perl? Or is that the task-* split-up in several *.bb you mentioned?
20:23.15likewisewhoops, too late
20:30.25*** join/#oe W8TVI (n=me@166.166.11.175)
20:52.03*** join/#oe pierrelux (n=pierre-l@144-125.sh.cgocable.ca)
21:09.10*** join/#oe NAiL_ (n=repvik@sql.kynisk.com)
21:13.30Laibschpolyonymous: I think you can consider yourself approved.  I recollect thumbs up from psokolovsky, hentges, koen and me (maybe more).  No objections.  You need to create your keys and send them to both mickey and koen.
21:13.53LaibschIf you are indeed not approved, they will let you know ;-)
21:15.27polyonymousLaibsch, okay, will do. <name>@openembedded.org from the phrasebook doesn't really imply @openembedded.org?
21:15.37Croftonyes it does :)
21:16.14polyonymousCrofton, but I don't have @oe.org address
21:16.20CroftonWe know
21:16.51polyonymousUmm... would you elaborate a bit on it so that it makes sense to me? :)
21:16.54CroftonI am not sure why it is that way, but I am pretty sure that is how it is
21:17.22polyonymousHmm..
21:17.28polyonymousIt's not that I object it, but I don't quite understand it either.
21:17.48Croftonme niether
21:18.15polyonymousthat makes me feel better, of course :)
21:18.30CroftonI am crofton@openembedded.org keywise
21:19.00polyonymousBut you have no corresponding email address?
21:19.04Laibschyes, this is just the key
21:19.13LaibschThere sometimes no adresses behind it
21:19.19LaibschMe, for example
21:19.33polyonymousYeah, I understand. I thought the purpose of using email is to ensure no collisions.
21:19.46LaibschI think that is suboptimal since of course everybody assumes this is a mail address and might try to contact the committer there.
21:20.01LaibschEspecially is this has worked with others in the past
21:20.03polyonymousthat too.
21:20.21LaibschBut no, this is not always an email address
21:20.22likewiseLaibsch: same here... maybe email forwarding is possible?
21:20.37LaibschI don't know
21:20.40CroftonI am sure there is a cunning plan
21:20.44Crofton:)
21:20.46Laibschand I don't really care *too* much
21:20.57Laibschthe plan is world domination
21:21.01Croftonright
21:21.06polyonymousI think it just ruins uniqueness constraint.
21:21.09*** join/#oe marcan_ (n=marcanso@160.10.7.121)
21:21.16polyonymousworking email is of no real concern here.
21:21.33Croftoncontact info is in maintainers
21:21.38Laibschmtn list keys will list one non-oe.org address
21:21.40polyonymousbut I think if I go for polyonymous I won't collide with anyone :)
21:22.00polyonymousnslu2-linux.org that is
21:22.10LaibschI think there is another one
21:22.12polyonymousno, way more
21:22.28polyonymous8 keys
21:22.47polyonymousmtn list keys|grep -v openembedded.org :)
21:23.02polyonymoushttp://rafb.net/p/9Et0Kr79.html
21:26.46polyonymousWell, if it's a custom here, I don't mind it. Just wanted to make sure, because it didn't make enough sense to me at the first glance.
21:28.13rwhitbymorning
21:28.20polyonymousgood one, I hope.
21:28.35LaibschCan we add somebody to the MAINTAINERS file who has no RW access to .dev but who is actively reporting and fixing bugs?
21:29.05polyonymousbeing in maintainers implies some responsibility, doesn't it?
21:29.23LaibschIt is not 100% clear what it implies
21:29.45LaibschThe only thing certain to me is that you volunteered to take care of XY
21:29.46polyonymousthat's true :)
21:29.55likewisepolyonymous: yes, you at least fix what you break :-)
21:30.05LaibschThere is also no screening really where you would have to pass some kind of test
21:30.07polyonymouslikewise, and vice versa :))
21:30.15likewisesssssh...
21:30.37polyonymousLaibsch, there is a stress-test of actually doing some work.
21:30.43likewiseLaibsch: then why did I have to buy two rounds of beer? :-)
21:30.43Laibschlikewise: Well, that would lead to the question of somebody "external" as MAINTAINER
21:30.59Laibschlikewise: Where?
21:31.04LaibschI did not get any!
21:31.05likewisejust kidding
21:31.22Laibschlikewise: Whatever it is you were proposing: DENIED
21:31.24Laibsch;-)
21:31.51likewiseActually, we (undetermined group of OE ppl) did have a few beers in FOSDEM.
21:33.12polyonymousI don't like beer.
21:35.28polyonymouspsokolovsky, I submitted the right patch.
21:35.34polyonymousNow I can generate some keys :)
21:37.44polyonymousI don't need to do anything with OE.mtn, do I? Just wonder why right before generating keys it states how to mtn db init OE.mtn...
21:38.24zeckepolyonymous: keys are saved in .monotone/
21:39.00polyonymouszecke, that's good. I was just thinking how do I preserve my private key if it goes to db :)
21:39.12zeckepolyonymous: it used to be in the db :)
21:39.21zeckepolyonymous: I think mtn 0.23 changed that
21:39.26polyonymousOh ... Exportable at least? :)
21:39.33polyonymousOr just keep a backup of the whole thing? :)
21:39.41zeckepolyonymous: exportable :)
21:40.06polyonymousthat's better :) Well, not that it matters now that it goes to ~/.monotone.
21:40.18polyonymousumm... it's ~/.monotone, not .monotone, I suppose?
21:40.32zeckeprobably
21:41.03polyonymoushmm.. why specify database for genkey ?
21:41.46zeckedunno
21:41.54polyonymousok. just wondering
21:42.40polyonymouszecke, I think it's outdated info.
21:42.59zeckeprobably
21:43.13polyonymousjust looking at monotone's doc.
21:43.27polyonymousI'm sorry for asking questions, just like knowing things I'm doing :)
21:46.49polyonymousand email addresses in the phrasebook are correct, I take it?
21:56.11CIA-403pfalcon 07org.oe.dev * rc3da8ddf... 10/ (3 files in 3 dirs): opie-todo cvs: Fix unbreak-logging.patch
21:56.15CIA-403polyonymous 07org.oe.dev * r63574aab... 10/ (6 files in 3 dirs):
21:56.15CIA-4qte 2.3.10: Fix lack of PAGE_* in latest linux-headers properly: use getpagesize()
21:56.15CIA-4* Closes #2201.
22:01.04*** part/#oe xjqian (n=gordon@71-85-151-212.dhcp.stls.mo.charter.com)
22:08.39*** join/#oe vervain_ (n=vervain@74-139-209-151.dhcp.insightbb.com)
22:16.37polyonymoussent it.
22:23.37*** join/#oe emte (n=emte@d64-180-45-14.bchsia.telus.net)
22:37.16*** part/#oe likewise (n=Leon_Woe@82-171-189-134.dsl.ip.tiscali.nl)
22:37.42*** join/#oe idealm (n=ideal@c58-107-18-60.belrs2.nsw.optusnet.com.au)
22:47.22Laibsch!oebug 717
22:47.23cdbot2* * Bug 717, Status: NEW, Created: 2006-02-23 01:16
22:47.24cdbot2* * Robert.Demski(AT)wp.pl: Include amule package bb files
22:47.27cdbot2* * http://bugs.openembedded.org/show_bug.cgi?id=717
22:47.43Laibschkoen, we need to add SlugOS to VERSION field
22:48.01*** join/#oe xjqian (n=gordon@71-85-151-212.dhcp.stls.mo.charter.com)
22:48.32LaibschCrazy, 72 bugs fixed in the last week.
22:48.41LaibschWell done!
22:57.58*** part/#oe ozstinger (n=ozstinge@216.143.234.167)
23:06.56polyonymousLaibsch, how're your qemu experiments?
23:29.44*** join/#oe CIA-30 (n=CIA@208.69.182.149)
23:33.39*** join/#oe emte_ (n=emte@d64-180-45-14.bchsia.telus.net)
23:33.43xjqianpolyonymous: how to make sure an old version of, e.g. glibc_intermediate, gets cleaned in tmp/staging
23:34.22polyonymousxjqian, why me? :) I don't know. I think staging doesn't keep track of files staged.
23:34.34Laibschpolyonymous: you mean the qem-native stuff?
23:34.37polyonymousso, maybe rm -rf tmp/ is the way to go :)
23:34.40polyonymousLaibsch, yes.
23:34.47polyonymousLaibsch, I know it compiled, but did glibc build?
23:35.14Laibschpolyonymous: I did not try.
23:35.25polyonymousLaibsch, ah ok. I did and it failed (with that patch).
23:35.25LaibschI don't have the CPU cycles to spare at the moment
23:35.36Laibschpolyonymous: OK, good to know
23:35.39polyonymousqemu segfaulted on glibc.
23:35.49LaibschPlease make a comment to that effect in the bug report
23:35.51xjqianpolyonymous: you seems awake:)  
23:35.51polyonymousIt would be better if it didn't fail, though :)
23:36.05Laibsch(S)
23:36.07LaibschLater
23:36.17JustinPxjqian: just address the channel for general questions
23:36.18polyonymousxjqian, awake and knowledgeable are different things :)
23:36.33polyonymousOkay, Laibsch, I'll comment.
23:36.43JustinPxjqian: packaged-staging *might* do it but I don't know. I've never gotten the damn  thing to work.
23:42.43*** join/#oe Crofton (n=balister@66-207-66-26.black.dmt.ntelos.net)
23:48.55xjqianJustinP: ok. thanks. My question is I'm not sure what's the best practice if a lib in the tool chain gets updated. How to make sure the old version is cleaned and not used anymore?
23:51.08JustinPxjqian: the right way would be for packaged-staging to work correctly and "upgrade" the packages in the stage environment
23:51.13JustinPxjqian: packaged-staging uses package management to install files to the staging folder(s)
23:51.35JustinPxjqian: like I said, though, it has never worked correctly for me. The author, koen, also doesn't seem interested in debugging the problem...
23:53.58xjqianJustinP: so the current practice for the devs are: cleaning up tmp, starting from a clean slate everytime anything important, e.g. glibc, gets an update? and for not so critical stuff, find a way (e.g. manually) to get by? Is my understanding correct?
23:54.10Croftonyep
23:54.52xjqianCrofton: thanks. I am all clear now8-)
23:55.25Croftonbasically, when you have time rm -rf tmp
23:55.29Croftonand rebuild
23:55.36JustinPwe would love someone else to work on packaged-staging...after koen's SoC project he seems to have abandoned it
23:55.48Croftonhopefully he has time this summer
23:55.57JustinPas far as I'm concerned it has never worked
23:57.02*** join/#oe Gerrath (n=Gerrath_@unaffiliated/gerrath)
23:59.55polyonymousrm -rf is a good thing - you can test if the fresh build works :)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.