**** BEGIN LOGGING AT Wed Jul 17 02:59:59 2013 Jul 17 06:21:46 hi all, I'm trying to build the backports (former compat-drivers and comapt-wireless) (http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/) in oe Jul 17 06:22:50 during the build process it tries to build and run a conf tool. this tool naturally does not run as it was build for the target architecture Jul 17 06:23:13 is there a standard way around such things? Jul 17 08:21:28 morning all Jul 17 08:30:25 morning Jul 17 09:14:56 hi all, I'm trying to build the backports (former compat-drivers and comapt-wireless) (http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/) in oe Jul 17 09:15:03 during the build process it tries to build and run a conf tool. this tool naturally does not run as it was build for the target architecture Jul 17 09:15:16 is there a standard way around such things? Jul 17 09:21:23 hii Jul 17 09:21:26 libxcb was skipped: Recipe is blacklisted: depends on blacklisted libxau, libxdmcp Jul 17 09:21:32 what is this error!!! Jul 17 09:22:01 when i try to build " libxcb " i'm getting that error! Jul 17 09:22:06 that libxcb was skipped, due to it depending on a blacklisted recipe, libxau, libxdmcp Jul 17 09:22:19 what more do you want to know Jul 17 09:22:50 where they are blacklisted?? how to i should make them whitelist Jul 17 09:23:05 i need to build xcb libs fro qt plugin linxcb Jul 17 09:23:07 johny_: http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html Jul 17 09:23:11 libxcb* Jul 17 09:23:12 search that for "whitelist" Jul 17 09:23:30 i have made in local.conf but still same error :-( Jul 17 09:23:44 made what? Jul 17 09:24:26 LICENSE_FLAGS_WHITELIST = in this i have added those two libxau, libxdmcp Jul 17 09:24:34 read the documentation Jul 17 09:24:39 that is not how to do it Jul 17 09:24:43 http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#enabling-commercially-licensed-recipes Jul 17 09:24:48 :O total documentation!! Jul 17 09:28:55 where could i see a log of an error if that happens during compilation? Jul 17 09:29:32 using bblayers Jul 17 09:34:00 nb-ben: the location of the log will be printing with the compilation error Jul 17 09:34:09 s/printing/printed Jul 17 09:34:42 im running with 6 threads Jul 17 09:34:49 ok Jul 17 09:34:52 i can hardly see letters Jul 17 09:34:54 lol Jul 17 09:35:06 what version are you running? Jul 17 09:35:31 and can you not scroll back up on your terminal Jul 17 09:36:03 it passed too quickly, though I found the log directory in the cache directory so I could grep that Jul 17 09:36:31 it's usually not that hard to locate, I run with 8 threads without issue... Jul 17 09:36:55 the process stops when it hits an error, so the last thing in your terminal, is the error... Jul 17 09:37:38 I guess in my case there were 5 more threads that had a lot to output then :P Jul 17 09:37:51 well, there is no output unless an error is hit.. Jul 17 09:38:13 unless you're using a version that more than ~1 year old Jul 17 09:38:50 in which case, I advise you to move to a new version Jul 17 09:57:32 chitz: there are two approaches - (a) unset CC LD etc. during do_configure (or add a separate task to do this) and then you can build the tool for the host within the same recipe; or (b) create a separate native recipe to build the tool that needs to run on the host Jul 17 10:32:02 morning all Jul 17 10:46:11 hi pb_ Jul 17 10:47:59 * liuyq is away: 我很忙 Jul 17 10:52:30 * zecke 不忙 :} Jul 17 10:53:13 * dm8tbr gets the electric hacksaw to cut down the shrubs, there must be letters hiding behind them! Jul 17 10:59:32 hi florian, zecke Jul 17 11:00:08 pb_: hey! Jul 17 11:00:33 * zecke tries to figure out why /proc/1/comm doesn't exist even when the kernel is new enough to support it. :} Jul 17 11:18:38 pb_: I assume you know GNU make a lot more than I do. I am dealing with systemd's Makefile. To generate the log file for failing tests they have a test-suite.log Makefile target. When a test is failing the test-suite.log target files and the file is removed. Do you know if GNU make can be tought to not unlink the file? Jul 17 11:22:29 zecke: mark it as .PRECIOUS, maybe? Jul 17 11:23:25 or, if you have .DELETE_ON_ERROR in your makefile, remove it :-} Jul 17 11:23:47 :} Jul 17 11:23:51 will sent an email Jul 17 11:23:52 thanks a lot! Jul 17 12:34:22 I ran bitbaker with 4 threads and 4 make processes on a hexacore machine, how would I go on about resetting it to 8 without ruining anything? Jul 17 12:35:23 I'm afraid that if I press Ctrl-C I will have to start the build all over again Jul 17 12:35:25 nb-ben_work: just change it Jul 17 12:35:38 oh, if I just change the configuration it will update on the go? Jul 17 12:36:15 update it and restart the build Jul 17 12:36:23 it will reuse what was already built Jul 17 12:36:26 with Ctrl-C ? Jul 17 12:36:34 (that's how I stop it?) Jul 17 12:36:38 y Jul 17 12:36:42 ah, alright Jul 17 12:37:18 also, I have read somewhere that if I run more than 4 threads it sometimes fails because of that Jul 17 12:37:26 does that make sense or is this bad information Jul 17 12:41:27 that sounds like bad information. Jul 17 12:41:40 I guess having too many threads could make your machine run out of memory, but apart from that it shouldn't do any harm. Jul 17 12:43:39 hopefully I can run it with 9 on 4GB Jul 17 12:43:58 this VPS cost me too much already to upgrade it lol Jul 17 12:44:21 I am thinking maybe one could do this on Amazon's cloud Jul 17 12:45:48 nb-ben_work: 9 PARALLEL_MAKE and 9 BB_THREADS? that's too much for 4GB ram Jul 17 12:46:07 yeah I think so too Jul 17 12:46:20 so far it seem like there's enough RAM though Jul 17 12:46:44 9 BB_THREADS will eat most of your memory Jul 17 12:46:59 it does use SWAM a little bit but most of the time there's like 300-500MB RAM free showing that most of that swapped data is not being accessed very often Jul 17 12:47:17 that's fine, this box is just debian with nothing else but the build running Jul 17 12:47:28 uh, nup, 20mb RAM left :D Jul 17 12:47:51 SWAP * Jul 17 13:02:07 hi all Jul 17 13:02:39 bluelightning, i saw on irc log that you were discussing about qt4 support in -c populate_sdk Jul 17 13:02:53 but from discussion it wasn't clear that. Jul 17 13:03:07 can you recall that in mind ? :) Jul 17 13:04:05 silvio_: all that's missing by default is the host tools Jul 17 13:05:30 yes qmake, moc, uic and so on.... how to add them in a bitbake -c populate_sdk ? Jul 17 13:05:47 where the image uses qt4 cross-compiled app... Jul 17 13:10:19 bluelightning: thanks for insane_skip tip the other day, worked perfectly :) Jul 17 13:10:52 bluelightning, wondering how to add the host tools in the build of the populate_sdk :) Jul 17 13:24:27 chris__: np Jul 17 13:24:40 silvio_: add TOOLCHAIN_HOST_TASK += "nativesdk-qt4-tools" to your image recipe Jul 17 13:25:26 JaMa, looks like 9 threads on 4GB works fine :) Jul 17 13:31:05 thanks Jul 17 13:36:38 nb-ben_work: that doesn't mean it's optimal, use bb-matrix if you want to know the optimal value Jul 17 13:38:03 of course a full bb-matrix test takes a while Jul 17 13:43:56 * JaMa is still running test-dependencies.sh script.. almost a week now Jul 17 13:43:57 I see Jul 17 13:44:44 3rd build.. Building recipe: firefox-l10n-ml (360/1848) Jul 17 13:45:08 I am building b2g for rpi with gstreamer support Jul 17 13:45:53 im at 1996/2934 Jul 17 13:46:09 it seem to be going pretty fast, it hasn't been over 2 hrs for sure Jul 17 13:47:27 openembedded's gstreamer is only 0.10 so it failed the first time :( Jul 17 13:47:38 I had to add meta-gstreamer1.0 Jul 17 13:47:40 JaMa: it's been running for a week? wow Jul 17 13:49:05 bluelightning: do you know if it is known that alignment.sh is not ran for systemd images? Jul 17 13:49:23 and somehow it seems gcc 4.8 generated unaligned memory access for the kernel VFS code. :} Jul 17 13:49:46 zecke: I've not seen any discussion of that Jul 17 13:51:02 I will do the lazy thing and file a bug report Jul 17 13:51:07 if there a distributed build system that would do what bitbake does across multiple machines? Jul 17 13:51:10 is * Jul 17 13:51:12 eren: yes, I should have started with smaller "world" :/ Jul 17 13:51:24 nb-ben_work: gst1.0 recipes are already in oe-core Jul 17 13:51:44 I couldn't find them in git.openembedded.org Jul 17 13:52:46 ah, I see now Jul 17 13:55:00 JaMa, I was looking here http://git.openembedded.org/meta-openembedded/tree/, it seem like that's what the rest of the stuff is coming from Jul 17 13:56:18 from meta-openembedded Jul 17 13:56:32 bluelightning, cool !! it works :) Jul 17 13:56:51 silvio_: :) Jul 17 13:57:05 I just don't understand how this works well enough lol, so I was looking for something that's named consistently with the rest of the meta-something packages Jul 17 13:57:15 nb-ben_work: you may find http://layers.openembedded.org/ useful as a way to find stuff as well Jul 17 13:57:29 bluelightning, taking a look at this Jul 17 13:57:30 it still miss the export DEFINES needed tought. does it works if I do TOOLCHAIN_HOST_TASK += "nativesdk-qt4-tools meta-toolchain-qt" ? Jul 17 13:57:50 ok I don't really understand the different between layers and recipes Jul 17 13:58:03 difference * Jul 17 13:58:05 silvio_: no, I don't think that is the right thing there Jul 17 13:58:14 o.O Jul 17 13:59:06 and where to ? the meta-toolchain-qt has the needed export DEFINES Jul 17 14:02:04 nb-ben_work: recipes are the actual 'build metadata'. recipes are put into layers, to better organize them. layers generally are used to group 'recipes' for specific features. Jul 17 14:02:18 ah I see Jul 17 14:02:19 the index lets you search for layers, and/or recipes Jul 17 14:02:25 so a layer is a collection of recipes Jul 17 14:02:38 oe-core is the 'base' layer, generally called 'meta' Jul 17 14:02:50 yes, that's correct. Jul 17 14:02:53 or it's a collection of recipes or other layers Jul 17 14:03:43 nb-ben_work: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#understanding-and-creating-layers Jul 17 14:04:12 a layer is a collection of recipes. i think you are confused because meta-oe git tree is a collection of layers ;-) Jul 17 14:04:12 bluelightning_, what about nativesdk-qt4-tools ? ... better solution ? Jul 17 14:04:14 nb-ben_work: also see the FAQ linked from the layer index front page Jul 17 14:04:56 nb-ben_work: a layer must have a configuration file in /conf/layer.conf Jul 17 14:05:05 there are many layers in meta-oe Jul 17 14:05:21 I see :P Jul 17 14:05:26 * nb-ben_work has an error :( Jul 17 14:05:28 ERROR: QA Issue: ntp: Files/directories were installed but not shipped Jul 17 14:07:54 nb-ben_work: check https://lists.yoctoproject.org/pipermail/yocto/2013-July/017184.html and the other answer in the same thread. Jul 17 14:09:10 thank you, sorry I'm such a noob lol, I didn't even know what to google and didn't get any results for my search Jul 17 14:15:27 I don't understand what files I should be moving where Jul 17 14:16:33 ndec, where could I learn more about how to resolve those paths? Jul 17 14:18:09 nb-ben_work: i suspect there must be some information in the doc. have you read the developer manual? Jul 17 14:18:20 not entirely Jul 17 14:18:36 but I'll have a closer look at that now Jul 17 14:20:01 nb-ben_work: basically, you build your component into its $WORKDIR, then you 'install' all the files from the build that you need to be packaged in $D Jul 17 14:20:18 from $D OE will create all your packages. Jul 17 14:20:28 what's $D? Jul 17 14:21:02 the variable that points to where you need to install your files. Jul 17 14:21:17 OE sets it up for you, so that you can use it in your recipe. Jul 17 14:21:25 each recipe gets a different $D value. Jul 17 14:21:31 ah, I see Jul 17 14:21:54 then OE uses the variables FILES_ to create the packages. Jul 17 14:22:13 e.g. FILES_${PN} = "${bindir}/* ${sbindir}/* ${libexecdir}/* ...... Jul 17 14:22:49 means that the package which has the same name of your recipe will include files from /usr/bin/* ,... Jul 17 14:23:04 all these variables are defined in meta/conf/bitbake.conf Jul 17 14:23:38 OE has reasonnable default for many packages: FILES_${PN}, FILES_${PN}-dev, ... Jul 17 14:23:51 yes I see Jul 17 14:24:08 I am still a little confused though, so I should make install to the appropriate location Jul 17 14:24:13 if your work install files in non standard place, then you can customize FILES_*** in your recipe. Jul 17 14:24:16 and then run again? Jul 17 14:24:21 you can git grep FILES_ for examples. Jul 17 14:24:43 yes. Jul 17 14:25:06 the recipe is what I gitted originally right? should not be in my build dir, but the parent dir Jul 17 14:25:22 or is the recipe being copied or fetched to my build dir somewhere Jul 17 14:26:21 sorry. i don't understand. Jul 17 14:27:09 ndec, I don't know where the .bb file for the recipe is located, or where the recipe is located :( Jul 17 14:28:34 nb-ben_work: hmm. what exactly are you trying to do. i might have missed the beginning. Jul 17 14:31:09 bluelightning_: hi. do you have any idea what this error means: ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored. Jul 17 14:31:22 it happens on a coworker PC, which i don't have access to. Jul 17 14:32:06 the end result is that some files are generated with pseudo as 'root', but the do_install later on fails, missing permission to access these files. Jul 17 14:34:22 ndec, my build failed because of that error :P Jul 17 14:34:33 so I am trying to make it build correctly, but I don't know what I need to move and to where Jul 17 14:35:18 nb-ben_work: what are you trying to build, and which version of OE are you using? and do you have any local modifications in your trees? Jul 17 14:36:15 I am trying to build rpi b2g, no modification. I fail on ntp for the error was have been talking about Jul 17 14:36:47 ndec, ^ Jul 17 14:37:47 hmm. ok. i thought you were doing your own recipe. well, in theory if you use a recipe from meta-oe, it should build ;-) Jul 17 14:38:14 I'll tell you where it's from Jul 17 14:38:17 i guess you use that one: meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.6p5.bb Jul 17 14:38:32 FWIW a generic solution to the problem is being worked out, I expect it'll be posted in the next few days Jul 17 14:38:47 yes Jul 17 14:38:58 bluelightning_: which problem? my 'pseudo' problem or ntp? Jul 17 14:39:06 ndec, I was just going to paste that :P Jul 17 14:39:08 ntp Jul 17 14:39:21 ok! Jul 17 14:39:43 ndec, do you know how I could fix that? :( Jul 17 14:41:08 i think you should be able to disable QA checks, but i am not sure, at least until the fix is done. maybe bluelightning knowns Jul 17 14:41:11 knows. Jul 17 14:41:37 nb-ben_work: if the problem is in master, you might prefer to use the 'stable' dylan branch instead. Jul 17 14:42:10 information on QA checks and how to control them: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-insane Jul 17 14:44:50 ndec, if I disable QA checks will I end up not having ntp in my build? Jul 17 14:56:42 bluelightning, cool two shots and I'm very happy :) Jul 17 14:57:06 silvio_: there's still the issue of the environment setup script Jul 17 14:57:10 I still noticed that I've two crossscripts which are not being moved in the SDK. the xmlrpc-c-config Jul 17 14:57:28 bluelightning, I solved with a toolchain_create_sdk_env_script_append :) Jul 17 14:57:49 now I have the crossscripts directory missing Jul 17 14:57:51 silvio_: sure, it would be nice if that were somehow taken care of in a more automated manner though Jul 17 14:58:13 I know Jul 17 15:03:37 bluelightning, so isn't any way. I should do by hand :( Jul 17 15:08:38 ndec, ERROR: QA Issue: ntp: Files/directories were installed but not shipped /lib/systemd/system/sntp.service /lib/systemd/system/ntpd.service Jul 17 15:08:51 ndec, how could I skip this check or make it just warn ? Jul 17 15:09:22 I have been trying to skip rpaths QA on all the ntp packages but that doesn't seem to have been the problem lol Jul 17 15:09:49 nb-ben_work: i don't know precisely, i have the same information you have (e.g. the link that bluelightning gave above) Jul 17 15:09:57 ah I see Jul 17 15:10:08 looks like it's useless-rpaths Jul 17 15:10:43 nb-ben_work: the error above is installed-vs-shipped not useless-rpaths Jul 17 15:10:54 ah Jul 17 15:11:08 that's undocumented then o.o Jul 17 15:11:51 nb-ben_work: right, and coincidentally I just sent the info to complete that section to our documentation writer this morning :) Jul 17 15:12:12 nb-ben_work: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4788 Jul 17 15:12:13 ah I see lol Jul 17 15:14:00 bluelightning, how would I skip that? I assume it would be adding INSANE_SKIP_ntp += "installed-vs-shipped" to ntp/ntp_4.2.6p5.bb , is that correct? Jul 17 15:14:27 nb-ben_work: that is one way yes Jul 17 15:14:44 :p if it works then that's good enough for me, for now :D Jul 17 15:15:57 YES Jul 17 15:16:05 ;p Jul 17 15:27:27 can I mix layers from meta-openembedded and openembedded-core ? Jul 17 15:28:43 only compatible versions (branches) Jul 17 15:29:48 uhh I need gstreamer0.10.36 from https://github.com/openembedded/oe-core/tree/master/meta/recipes-multimedia/gstreamer, but I have been getting my layers from openembedded-meta Jul 17 15:30:05 or I could use any other gstreamer0.10 that is higher than 0.10.33 Jul 17 15:37:14 JaMa, oe-core/meta/recipes-multimedia is not a layer, right? Jul 17 15:37:42 or is it a layer? and if so can I replace openembedded/meta-multimedia with it? Jul 17 15:38:18 nb-ben_work: no Jul 17 15:38:29 nb-ben_work: it's time to read some basic documentation... Jul 17 17:43:44 fyi, looks like meta-oe's tracker recipe from meta-oe isn't buildable without meta-gnome, as it rdepends on gvfs Jul 17 17:43:47 heh Jul 17 18:03:06 this may sound kinda stupid, but is there an ldd-like command i can use to look for missing symbols in cross-comiled libs? Jul 17 18:03:21 on an x86 host i mean... Jul 17 18:04:08 not sure. ldd runs ld-linux on the binary, so such a tool would have to be completely different, since it can't run the linker against it Jul 17 18:04:16 hmm Jul 17 18:04:34 looks like the cross toolchain bin dir has nm, objdump, and readelf... Jul 17 18:05:05 if the symbol was missing at build timem, it would never have successfully linked, so i'm assuming you're trying to sanity check a sysroot or somethinga fter the fact? Jul 17 18:05:18 i need to find an under-linked lib... Jul 17 18:06:53 we have a local app that is linking against cairo(et al) and without -lz in his linker args he gets missing zfoo symbol errors Jul 17 18:07:51 you shouldn't be relying on implicit linking anyway with recent toolchains, it's entirely disabled on some systems. Jul 17 18:08:01 in other words, he should link -lz, or use pkg-config Jul 17 18:08:02 :) Jul 17 18:09:09 afaik, anyway Jul 17 18:11:42 well, he's not using libz directly at all Jul 17 18:12:01 which points to one of the other libs being under-linked Jul 17 18:20:08 ah, right, the change i was thinking about just makes the explicit link necessary if it's used explicitly Jul 17 18:20:11 fair enough Jul 17 18:21:14 playing with readelf to see what kind of symbol info i can get... Jul 17 18:22:32 mr_science: iirc, mklibs has to resolve all symbols in order to minimize the libs when processing the rootfs. add the bits to a filesystem and enable mklibs use with it? Jul 17 18:22:36 might be worth a try anyway Jul 17 18:23:23 hmm, not familiar with that one... Jul 17 18:23:46 is it something i can use in oe-classic? Jul 17 18:24:28 no idea Jul 17 18:24:37 it strips out symbols from libs which are't used by anything in the fs Jul 17 18:24:45 good for images you'll never add to at runtime Jul 17 18:39:25 ugh Jul 17 18:39:49 looking at some almost-never-used linker options Jul 17 18:40:02 almost never for me, anyway... Jul 17 18:40:05 for some reason I am struggling to understand why I can't find gstreamer0.10.36 from poky Jul 17 18:40:35 its been a few hours that I am reading the documentation and searching files to understand Jul 17 18:41:17 anyone know how I would go on about "enabling" multimedia recipes from poky Jul 17 18:41:37 depends on your layer config Jul 17 18:41:52 do you know what I should be looking for in the layer config? Jul 17 18:42:18 you would add the appropriate layer to your bblayers.conf Jul 17 18:42:39 which recipe trees are you building from? Jul 17 18:42:58 meta-openembedded, and poky Jul 17 18:43:03 hold on, I'll paste my bblayers.conf Jul 17 18:43:49 http://pastebin.com/GQE3nStt Jul 17 18:43:51 this is how it looks Jul 17 18:43:55 gstreamer shoudl be in one of the meta-openembedded layers i believe Jul 17 18:44:23 yeah but it's 0.10.8 Jul 17 18:44:29 and I need at least 0.10.36 Jul 17 18:44:40 that sounds too old... Jul 17 18:45:12 yep there's gstreamer1.0.8, but unfortunately b2g will only accept 0.10.33* or above Jul 17 18:46:04 which branch are you building from? Jul 17 18:47:05 branch for OE? Jul 17 18:47:17 branch in meta-openembedded Jul 17 18:47:42 master I believe Jul 17 18:47:49 let me check Jul 17 18:48:36 yeah, master Jul 17 18:49:12 i only see a couple of ancillary gstreamer recipes browsing the web interface... Jul 17 18:49:34 where are the core gstreamer recipes? Jul 17 18:49:47 * mr_science left his poky build setup at home Jul 17 18:50:52 the openembedded-core ? Jul 17 18:50:54 is that the djwillis meta-raspberrypi layer in your config? Jul 17 18:51:24 nope, imphilips Jul 17 18:51:35 imphil * Jul 17 18:51:58 hmm, haven't really looked at any of the other forks Jul 17 18:52:03 ah. sorry.. my brain doesn't work anymore Jul 17 18:52:10 it's the one from the yokto project Jul 17 18:52:14 master branch aswell Jul 17 18:52:37 i've added a bunch of recipes to my fork, but no new gstreamer stuff Jul 17 18:52:58 yeah, i think yocto and djwillis are synced up Jul 17 18:53:30 what are you looking for in terms of rpi functionality? Jul 17 18:55:30 mr_science, I want b2g (boot to gecko) with gstreamer Jul 17 18:56:16 so it can play h.264 movies Jul 17 18:56:57 well, unless there's another layer with gstreamer stuff, you'd need to bump recipe versions Jul 17 18:58:29 if I include openembedded-core layer along with those layers Jul 17 18:58:37 think it will work? Jul 17 19:01:16 it should if it's a current meta-layer Jul 17 19:02:08 otherwise let me know and i can look at adding some newer gstreamer recipes to my meta-pi layer... Jul 17 19:02:40 it already has mpd/audio/openbox Jul 17 19:02:59 I think I know what I did wrong Jul 17 19:03:12 I didn't add dependency for gstreamer anywhere Jul 17 19:08:20 gah, tracker has all sorts of bugs with automaitcally pulling in deps if they're available Jul 17 19:08:26 we need to add a pile of PACKAGECONFIGs Jul 17 21:33:41 nb-ben_work: now that you've made me curious, i'll see what versions of gstreamer/gst-plugins are in my pi image Jul 17 22:13:32 ant_home: is spitz kernel working for you when built with gcc-4.8? Jul 17 22:14:24 yes, I've tested pxa255 Jul 17 22:14:54 I can test spitz now Jul 18 02:29:16 * nerdboy abuses the linker as a workaround for someone else's build issues... Jul 18 02:30:04 it's only a one-off debug build, so hopefully it'll Just Work **** ENDING LOGGING AT Thu Jul 18 02:59:58 2013