**** BEGIN LOGGING AT Sat May 09 06:24:15 2009 **** ENDING LOGGING AT Sat May 09 06:35:11 2009 **** BEGIN LOGGING AT Sat May 09 06:35:40 2009 **** ENDING LOGGING AT Sat May 09 06:40:32 2009 **** BEGIN LOGGING AT Sat May 09 06:41:03 2009 May 09 06:48:48 ant__: I'm still struggling with that gtk+ error :-( May 09 08:41:29 hi everyone. I got the following error during an x11-image build of kaeilos with the oe stable branch: May 09 08:41:30 NOTE: Tasks Summary: Attempted 27 tasks of which 0 didn't need to be rerun and 3 failed. May 09 08:41:31 ERROR: '/home/koan/devel/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb' failed May 09 08:41:31 ERROR: '/home/koan/devel/openembedded/recipes/quilt/quilt-native_0.46.bb' failed May 09 08:41:31 ERROR: '/home/koan/devel/openembedded/recipes/gnu-config/gnu-config-native_20050701.bb' failed May 09 08:41:50 I found an old forum post sayiing that it may depend on concurrency problems... May 09 08:42:06 anyone know if this is true? should I run it all in one thread? May 09 08:47:26 hi everyone. I got the following error during an x11-image build of kaeilos with the oe stable branch: May 09 08:47:26 NOTE: Tasks Summary: Attempted 27 tasks of which 0 didn't need to be rerun and 3 failed. May 09 08:47:26 ERROR: '/home/koan/devel/openembedded/recipes/stage-manager/stagemanager-native_0.0.1.bb' failed May 09 08:47:26 ERROR: '/home/koan/devel/openembedded/recipes/quilt/quilt-native_0.46.bb' failed May 09 08:47:26 ERROR: '/home/koan/devel/openembedded/recipes/gnu-config/gnu-config-native_20050701.bb' failed May 09 08:47:27 I found an old forum post sayiing that it may depend on concurrency problems... May 09 08:47:29 anyone know if this is true? should I run it all in one thread? May 09 08:53:05 hello May 09 09:56:52 roland_: hi, which distro are you using there? May 09 09:58:17 hello again :) kaeilos 4.04 May 09 09:58:34 i am buillding it now without concurrency... hence no problems May 09 09:59:22 i mean yet no problems :) task 119/4000 May 09 10:01:42 roland_: on host system? debian, unbuntu, etc... May 09 10:01:58 XorA|gone: ping May 09 10:07:09 ubuntu intrepid May 09 10:07:17 i changed back to gcc 4.1 as recommended May 09 10:13:57 03Koen Kooi  07org.openembedded.dev * r004ff78c40 10openembedded.git/conf/checksums.ini: checksums.ini: add some checksums May 09 10:14:08 03Koen Kooi  07org.openembedded.dev * r585a4edbc9 10openembedded.git/ (6 files in 3 dirs): May 09 10:14:08 webkit-gtk: bump SRCREV, fix gtk-doc, fix packaging May 09 10:14:08 * runtime tested on beagleboard with midori and epiphany May 09 10:14:08 03Koen Kooi  07org.openembedded.dev * re9e1a54b27 10openembedded.git/recipes/efl1/ecore_svn.bb: ecore: bump PR May 09 10:14:11 03Koen Kooi  07org.openembedded.dev * r8f67184683 10openembedded.git/ (conf/checksums.ini recipes/gtk-webcore/midori_0.1.6.bb): midori: add 0.1.6 May 09 11:08:00 gm mickey|breakfast :-) May 09 11:08:51 HopsNBarley_: hello, long time no see/talk. How are you? May 09 11:30:55 wow, Laibsch :) May 09 11:31:11 morning pplz :) May 09 11:31:15 good morning! May 09 11:31:39 I'm still having problems with gcc-cross May 09 11:31:57 And the log looks very similar to the one I had yesterday May 09 11:31:59 :-( May 09 11:34:48 yesterday's log: http://tinderbox.openembedded.net/public/logs/5008489.txt May 09 11:37:32 today's log (after installing gfortran, libmpfr-dev and libgmp3-dev as advised by zecke): http://tinderbox.openembedded.net/public/logs/5034501.txt May 09 11:37:48 The build host is Ubuntu hardy May 09 11:38:41 It's some kind of fortran problem, that much I learned May 09 11:41:49 what does config.log say? May 09 11:42:35 it does look like some kind of fortran issue, but you'd need to establish what is causing configure to think that fortran is "not working". May 09 11:43:26 (incidentally, it'd be easier to read the log if you ran it without -j3, otherwise the output from different configure instances gets all jumbled together.) May 09 11:43:28 "fortran" is the symptom May 09 11:43:36 Laibsch: try to disable parallel make at first :) May 09 11:43:42 phew building image on one thread one core is slow May 09 11:44:06 OK May 09 11:44:30 Do I have to run "bitbake -c clean gcc-cross" or can I just retry the build? May 09 11:44:34 btw, I should not have fortran too.. May 09 11:44:39 It takes VERY long on my slow machine May 09 11:44:50 Just retry the build, there's no need to clean it. May 09 11:44:51 rebuild should be enough imho May 09 11:44:56 cool May 09 11:45:07 But you might as well check config.log first, it might well be illuminating. May 09 11:46:28 yes, true May 09 11:49:20 sorry for perhaps stupid question but does the build process of an image generally go faster towards the end? Im at task 176/4000 after 3 hours :( May 09 11:50:37 I hope /export/oe/tmp/angstrom/org.openembedded.dev/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.2.4-r6/gcc-4.2.4/build.i686-linux.arm-angstrom-linux-gnueabi/config.log is the one you want: http://rafb.net/p/fsUUcx25.html May 09 11:50:59 FWIW, /export/oe//tmp/angstrom/org.openembedded.dev/staging/i686-linux/usr/include has mpfr.h and gmp.h May 09 11:51:12 roland_, losely speaking yes May 09 11:51:23 gcc and glibc take a while May 09 11:51:33 ok im through with them i think May 09 11:51:41 qemu took a while too May 09 11:51:44 roland_: what machine are you compiling on? how much ram? May 09 11:51:52 pb_: There are a lot of other config.log files, I hope I looked at the right one May 09 11:51:58 too little ram will kill performance May 09 11:51:58 ubuntu intrepid, but virtualized May 09 11:52:06 so I think 1 gb ram May 09 11:52:12 1 gb is little May 09 11:52:45 ok... also im running in one thread 1 core, beacuse i got errors doing it parallell May 09 11:52:46 I'm building angstrom x11-image on Semphron2800+/512Mb RAM May 09 11:52:47 Laibsch: you need the one that it was trying to configure in when it failed. might be more obvious which one that is if you run without -j3 May 09 11:52:51 bbiab, gotta go visit the mother in law May 09 11:52:54 ~10-12 hours May 09 12:48:39 raster: hola May 09 12:51:46 yo z. May 09 12:53:31 I did not clean gcc-cross and now bitbake goes straight to the compile task May 09 12:53:38 I assume it will fail again May 09 13:06:45 are you using packaged staging with deploy dir outside tmp dir, by any chance? May 09 13:10:02 don't think so May 09 13:10:14 my config is rather straight-forward May 09 13:10:18 Let me dig it out May 09 13:11:00 packaged staging always breaks for me when I'm using a deploy dir outside tmp dir (which actually is the usecase for which packaged staging was done for IMO... but anyways) May 09 13:11:03 http://rafb.net/p/eJguyI76.html May 09 13:11:07 is my config May 09 13:11:32 since I pasted that I commented out the parallel compilation stuff May 09 13:11:39 hmm, no idea what kind of funny things your selected distro is doing May 09 13:11:48 zecke|away: yo yo! May 09 13:11:50 but you definitely don't change deploydir May 09 13:11:54 so that's not the problem May 09 13:12:08 mickeyl: I think it's the same distro you are using ;-) May 09 13:12:12 no it's not May 09 13:12:23 I think I am missing some packages or something May 09 13:12:36 mickey@andromeda:/local/pkg/oe/om-gta02$ cat conf/local.conf |grep DISTRO May 09 13:12:36 DISTRO = "minimal" May 09 13:12:38 mickeyl: you said yesterday you compile on Ubuntu, no? May 09 13:12:41 zecke|away: bugger. time to offline. cu later! :) May 09 13:12:44 yes, jaunty atm. May 09 13:12:54 i was referring to OE distro May 09 13:12:56 mickeyl: oh, the target distro ;-) May 09 13:12:56 not host distro May 09 13:13:08 Maybe I will change and see if that helps May 09 13:42:04 can we rename minimal to something describing it better? May 09 13:42:18 people seem to be getting confused with it and micro May 09 13:51:33 I reran bitbake for gcc-cross without cleaning, but with parallel compilation disabled: http://tinderbox.openembedded.net/public/logs/5048571.txt May 09 13:52:26 I believe /export/oe/tmp/angstrom/org.openembedded.dev/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.2.4-r6/gcc-4.2.4/build.i686-linux.arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi/libgfortran/config.log is the config.log we are looking for: http://rafb.net/p/0N3PkQ15.html May 09 13:52:38 I'm not sure how to read that config.log May 09 14:15:05 Laibsch, line 218 looks bad May 09 14:16:04 :0: internal compiler error: Illegal instruction May 09 14:16:24 I'm not sure why this only seems to happen to you May 09 14:16:38 thanks for taking a look May 09 14:17:10 some form of compiler issue :( May 09 14:17:54 fwiw I build 4.3.3 for beagle/armv7a May 09 14:17:59 what machine again? May 09 14:19:08 Here is what I have installed as far gcc is concerned May 09 14:19:10 http://rafb.net/p/I8if9V71.html May 09 14:19:25 the target machine is qemuarm May 09 14:19:25 what MACHINE are you builindg for? May 09 14:19:29 ah May 09 14:19:59 does anyone else build for that machine? May 09 14:20:33 don't know May 09 14:20:37 I can try another one May 09 14:20:44 Here is more info about my gcc situation May 09 14:20:47 http://rafb.net/p/5j2Tu874.html May 09 14:20:52 gcc points to 4.2 May 09 14:21:05 I'll try machine spitz May 09 14:21:42 look in the distro config to see what gcc version will get built May 09 14:22:30 OK May 09 14:22:33 | checking if /export/oe/tmp/angstrom/org.openembedded.dev/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.2.4-r6/gcc-4.2.4/build.i686-linux.arm-angstrom-linux-gnueabi/./gcc/xgcc supports -c -o file.o... (cached) yes May 09 14:22:42 makes me think it will be 4.2.4 May 09 14:22:45 I'll confirm May 09 14:24:10 tmp/cross/armv7a/bin/arm-angstrom-linux-gnueabi-gcc -v May 09 14:24:34 looks right: ANGSTROM_GCC_VERSION ?= "4.2.4" May 09 14:24:34 (from /export/oe/openembedded.org/conf/distro/angstrom-2008.1.conf) May 09 14:24:48 ok, I need to go back to looking at linphone May 09 14:27:44 thanks, Crofton May 09 14:27:46 http://rafb.net/p/dnabAj22.html May 09 14:28:00 is the output and some info about the cross gcc May 09 14:28:40 which also says 4.2.4 May 09 15:00:52 hmm, linphone wants a libosip2 header that does not exist in osip2 :) May 09 15:04:26 03Andrea Adami  07org.openembedded.dev * r2d94bdad65 10openembedded.git/recipes/gpe-clock/ (5 files): May 09 15:04:26 gpe-clock: skip fix-install patch: sources are ok since 0.27 May 09 15:04:26 - apply patch only to revisions between 0.21 and 0.25 May 09 15:28:07 g'day mickeyl May 09 15:28:13 hey pb__ May 09 15:28:16 does not look like a machine problem, spitz fails, too: http://tinderbox.openembedded.net/public/logs/5050084.txt May 09 15:29:08 the error is different for spitz, though May 09 15:30:09 that looks like the same error to me May 09 15:30:13 did you look in config.log? May 09 15:30:18 "configure: error: GNU Fortran is not working" May 09 15:30:26 pb_, you saw the compiler error? May 09 15:30:34 you really do need to locate the right config.log and find out what's going on with that May 09 15:30:43 pb_, scroll back :) May 09 15:30:44 Crofton: no, I was at my mother-in-law's. what was the compiler error? May 09 15:31:11 I'll retry with beagleboard now May 09 15:31:22 http://rafb.net/p/0N3PkQ15.html May 09 15:31:25 line 218 May 09 15:31:26 oh, right, I see, illegal instruction May 09 15:31:31 that's rather a funky one May 09 15:31:31 The problem with troubleshooting is that I have limited knowledge what to look for May 09 15:31:38 heh May 09 15:31:44 Laibsch, it is a funky error May 09 15:31:54 beagle uses different gccc May 09 15:32:09 I'll take that as "not easy to troubleshoot even for cracks" :-) May 09 15:32:15 right May 09 15:32:26 Yes, I want to see if a different gcc does not generate the same error May 09 15:32:30 limited pool of people know enough May 09 15:32:40 AFAICT, qemuarm and spitz are fairly similar machines for OE May 09 15:33:32 certainly difficult to troubleshoot remotely. it basically means that either gfortran-4.2.4 is just plain broken in your configuration (which isn't impossible by any means) or that it's being wrongly compiled by your host toolchain (which is unlikely but again certainly not impossible) May 09 15:34:09 trying a different version of gcc-cross probably is the right place to start, 4.2.4 is fairly old May 09 15:34:43 pb__: is 4.1 still the best for ARM? May 09 15:35:01 if you wanted to try to debug it directly, the place to start would be to take the command that configure is running (i.e. the line just before the error), run it under gdb, and see where it blows up. May 09 15:35:02 or did they fix their arm optimization in 4.3.x / 4.4? May 09 15:35:17 mickey|sofa: unfortunately there doesn't seem to be any one "best" version for arm, different versions lose in different ways. May 09 15:35:28 ah bummer May 09 15:35:31 4.1 probably is the best for plain c/c++ if you don't need thumb May 09 15:35:48 beagle needs latest for armv7a support :( May 09 15:36:05 afaik, "that" optimisation bug is still in 4.4 but I haven't checked recently May 09 15:36:29 Crofton: presumably you don't strictly _need_ to compile most programs for armv7a though, right? May 09 15:36:32 hmm, how can a problem like that persist over so many versions? May 09 15:37:09 mickey|sofa: because it seems to be hard to fix it for arm without causing other (sadly more important to the gcc steering committee) targets to regress May 09 15:37:24 this is unfortunately a fairly common problem with gcc middle-end issues May 09 15:37:33 I've got a Netvista 8363 thin client which has a borked bios which boots the machine by executing the file kernel.2x00 with some pre-defined commandline arguments (one of them being root=), which is supposed to be a linux kernel vmlinux, but I suppose that it could be any static ELF executable. I would like to run a decent bootloader instaead of this. Is altboot what I need? Or syslinux perhaps? May 09 15:37:35 ah, ok, that makes some sense May 09 15:37:42 i reckon it's the same with glibc? May 09 15:37:58 pb_, what fun would that be :) May 09 15:38:09 bbiab, gotta go do some shopping now May 09 15:38:11 I do care about NEON and newer instructions May 09 15:38:12 have fun May 09 15:38:13 l8r May 09 15:39:42 03Philip Balister  07org.openembedded.dev * r6f53c97f54 10openembedded.git/ (4 files in 2 dirs): May 09 15:39:42 ortp-0.13.1 : Add later version of ortp. Convert to use .inc. May 09 15:39:42 * There are later versions, but this version is needed May 09 15:39:42 for openbts. May 09 15:39:43 03Philip Balister  07org.openembedded.dev * r9040ed48ea 10openembedded.git/recipes/u-boot/u-boot_git.bb: u-boot_git.bb : Update FILESPATHPKG to include u-boot-git directory. May 09 15:39:55 pb_: thanks for your help. which version would you suggest 4.4.0 or 4.3.3? May 09 15:40:36 i would fear .0 version :) May 09 15:40:56 4.3.3, then? May 09 15:41:02 or something else? May 09 15:41:04 that is what i would try May 09 15:41:07 mickey mentioned 4.1 May 09 15:41:13 OK, will do May 09 15:41:14 thanks May 09 15:42:39 gl May 09 15:50:15 mickey: does your "minimal" distro have multi-machine support? May 09 15:51:52 i think so May 09 15:51:58 it's merely a sanitized copy of angstrom May 09 15:52:00 cool May 09 15:52:01 no longer minimal May 09 15:52:12 I think I may give that a try one of these days May 09 15:52:13 thus should be renamed (again) to generic or whatever May 09 15:52:26 and release a deb package for apt-getable OE for it May 09 15:52:35 if you want some new vala goodness or python, check out my tree @ git.freesmartphone.org May 09 15:52:55 don't even understand what that would get me ;-) May 09 15:53:06 good, then it's probably not relevant for you May 09 15:53:18 I just want things to get compiling again May 09 15:53:34 Then I will need to think about how to deal with my underpowered machine ;-) May 09 15:53:48 right May 09 15:53:53 you need some CPU cycles May 09 15:54:11 I certainly do May 09 16:03:10 otavio: do you have OE commit access? May 09 16:05:28 he has May 09 16:07:32 crap, I forgot to sort checksums :) May 09 16:14:11 03Philip Balister  07org.openembedded.dev * r9b19676d7e 10openembedded.git/conf/checksums.ini: checksums.ini : Sort checksums. May 09 16:48:45 hmm, funny messages while building numpy .... May 09 16:56:18 hi all... still trying to build kaielos 4.04 on an ubuntu 8.10 machine with gcc 4.1.. anyone recognizes this problem?: http://tinderbox.openembedded.net/public/logs/5047071.txt May 09 16:57:09 basically cross-compile fails with error : cc1: error: unrecognized command line option "-Wno-overlength-strings" May 09 17:05:43 cbrake_away: yes, i do May 09 17:13:59 roland_: are you aware of http://wiki.openembedded.net/index.php/Gcc_issues_in_Intrepid_and_later ? May 09 17:24:26 octavio was that to me? May 09 17:24:42 ? May 09 17:24:52 ah sorry nothing May 09 17:24:56 heh May 09 17:24:56 ok May 09 17:45:33 anyone knows if it smells trouble to change gcc version during an image build? I had a problem after like 200 tasks so Im switching from gcc 4.1 to 4.3 May 09 17:45:49 now i don't get the error but dont know if the final image will like this May 09 17:46:02 that sounds like trouble May 09 17:46:08 ok so delete tmp? May 09 17:46:13 yeah May 09 17:46:17 safest May 09 17:46:29 thanx May 09 17:46:59 ld May 09 17:47:18 ld: no input files May 09 17:47:28 :) May 09 17:49:07 ls May 09 17:49:12 ops again damn it May 09 17:49:17 rolleboy, focus :) May 09 17:50:07 virtualization is nice but maaany windows :) May 09 19:17:44 03Andrea Adami  07org.openembedded.dev * r77ee21683f 10openembedded.git/recipes/gpe-mixer/ (gpe-mixer/fix-install.patch gpe-mixer_0.42.bb): gpe-mixer: fix Makefile - don't strip on install May 09 19:47:20 re May 09 20:30:18 florian, hi May 09 20:31:24 hi Crofton|work May 09 20:32:52 * florian notices porting a NAND driver from an ancient MTD to recent is really nasty May 09 20:38:32 ug May 09 20:57:33 ah.bad evening for fetching from *.linuxtogo :/ May 09 20:58:46 ant__: hey :) May 09 20:58:56 I see some activity :) May 09 20:59:09 hi Jay7 May 09 20:59:11 florian: did you mean kernel driver? May 09 20:59:58 florian: my gpe-image struggles fetching gpe stuff from angstrom mirror... May 09 21:00:30 florian: good evening May 09 21:00:51 EHLO pb_ May 09 21:01:04 _ May 09 21:01:23 hi ant__ May 09 21:01:30 pb__: my tail is as long as yours May 09 21:01:34 ;) May 09 21:02:05 heh, exactly what I was just thinking May 09 21:02:23 Jay7: yes... well almost May 09 21:02:50 * Jay7 fears that zaurus will be affected too May 09 21:03:04 I'm porting an old uboot nand driver to a recent linux May 09 21:03:20 ant__: I can fix this I guess May 09 21:03:21 ah, uboot.. May 09 21:03:55 ant__: should be better now May 09 21:04:15 rosetta fetched!...thx May 09 21:04:56 hello May 09 21:05:00 hehe.. my Tosa should be delivered ~ May 27th May 09 21:05:21 can somebody help me with finding out the pinlayout for the jtag connector May 09 21:05:26 when someone will donate me other unused device in US - welcome ;) May 09 21:05:48 it is for a box adb-5810 May 09 21:06:13 would like to flash it and put a linux on it May 09 21:08:06 krisse: hmm... do you have some info about this device? May 09 21:10:32 what do you need? May 09 21:10:42 the chipset? May 09 21:11:23 it was used before as setup box (decoder for dvb-C channels May 09 21:11:44 more info here:http://www.adbglobal.com/files/ADB_datasheet_5810CDX.pdf May 09 21:12:09 florian: is this wat you need? May 09 21:15:20 03Andrea Adami  07org.openembedded.dev * r1b6428c44b 10openembedded.git/recipes/startup-monitor/ (files/makefile-fix.patch startup-monitor_0.18-2.bb): startup-monitor: fix makefile - don't strip on install May 09 21:16:44 krisse: ok, looks interesting. and they advertize that there is linux running on it already :) May 09 21:17:17 it might be an option to search for a serial interface.. maybe you can just talk to the bootloader. May 09 21:18:40 I found the debug port May 09 21:18:42 4 pin May 09 21:18:48 I created a serial adaptor for that May 09 21:19:04 and only thing I get is when booting DebugReady message May 09 21:19:12 and a strange prompt May 09 21:19:19 something like ]] May 09 21:20:21 and when I try to send some letters it does not echo them May 09 21:20:28 ah nasty May 09 21:20:28 I suppose they have locked that May 09 21:20:36 yes maybe May 09 21:21:10 maybe try to hold a button while powering on... May 09 21:21:23 hmm May 09 21:21:25 good id May 09 21:21:29 lets try May 09 21:23:49 florian: gpe-image now built! May 09 21:27:25 florian: does not change May 09 21:27:38 tried with power button May 09 21:28:13 ant__: wee cool! May 09 21:28:30 krisse: ah too bad May 09 21:29:15 just power-on sounds too easy :) May 09 21:31:35 florian: any id on jtag pinlayout? May 09 21:34:13 krisse: have you photos of the board(s)? May 09 21:36:59 krisse: http://www.jtagtest.com/pinouts/ May 09 21:37:19 ant__: thx will try that May 09 21:37:24 krisse: there are some common ones... what do you know about the chipset? May 09 21:37:50 "There are two major JTAG header arrangements used in SOHO routers based on MIPS CPUs. One uses 12 pins and the other uses 14 pins." May 09 21:37:55 ^^OpenWrt May 09 21:38:27 but four or five is also fine May 09 21:40:21 cpu is a st7109 May 09 21:41:12 near it you can find the following chip witch is the flash I suppose m28w320hs May 09 21:49:21 florean: do you need more info? May 09 21:49:37 florian: any idea about "locale_base_ar_kw" ? Arabic Kuwait? Default?? May 09 21:53:58 one sec May 09 21:54:42 ant__: huh... no not default May 09 21:55:48 I have it in *all* my images built recently May 09 21:56:06 krisse: do you have any connectors or pads looking like they might be a jtag connector? May 09 21:57:10 florian: look at your .dot files in -testlab May 09 22:08:17 florian: 'gdk-linux-fb-2.0' again :/ May 09 22:08:28 it is x11-gpe-java-image May 09 22:17:14 ant__: we need a bitbake command "what-pulls-in" ;) May 09 22:17:35 I suspect gdk-pixbuf May 09 22:18:04 looking at the .pc files now May 09 22:18:47 florean: sorry for late reply yes. there is 1 connector 20 pin that I think is the jtag May 09 22:20:49 krisse: ah cool... 20pin i like to be a standard arm jtag May 09 22:21:16 florian: the 3 gdk-*.pc files are changed May 09 22:21:44 gdk-x11 unchanged May 09 22:22:15 florian: argh... May 09 22:22:17 target=linux-fb May 09 22:22:29 gdk-2.0.pc May 09 22:23:17 ant__: eeks May 09 22:23:50 I'm diffing now, will paste May 09 22:30:19 florian: http://rafb.net/p/PwMQqO34.html May 09 22:36:58 * Jay7 -> sleep May 09 22:39:19 ant__: strabge May 09 22:39:23 eh strange May 09 22:40:22 florian: it seems (tinderbox) that libhildon was the precedent package built May 09 22:46:59 florian: my logs says these were staged at 00.03, exactly like gdk-pixbuf-2.10.14-r2 May 09 22:47:31 and yes, same old version May 09 22:50:45 florian: log_populate_staging_postamble of gdk-pixbuf May 09 22:50:49 http://rafb.net/p/FgB5Ak67.html May 09 22:51:43 argh ..gtk+-2.0.pc too May 09 22:51:51 target=linux-fb May 09 22:52:27 argh ..gtk+unixprint-2.0.pc too May 09 22:52:33 oh..boys May 09 22:52:38 wtf May 09 22:58:05 florian: found...gdk-pixbuf_2.10.14.bb May 09 22:58:20 EXTRA_OECONF = "\ May 09 22:58:20 --without-x \ May 09 22:58:20 --with-gdktarget=linux-fb \ May 09 22:58:20 ... May 09 23:19:36 * florian fells asleeo May 09 23:19:40 good nigt May 09 23:23:56 'nite **** ENDING LOGGING AT Sun May 10 02:59:57 2009