**** BEGIN LOGGING AT Tue Sep 02 02:59:59 2014 Sep 02 06:56:07 morning Sep 02 06:57:04 can I disable sstate-cache for just one recipe? I have a 3rd party recipe that behaves badly and I don't really want to spend time fixing it and keeping that fix up-to-date. Sep 02 07:26:15 good morning Sep 02 07:40:19 hi, I have problem in "do_compile" task of "qt4-x11-free" package. How can I solve this? I have this problem in both Ubuntu & Gentoo. Sep 02 07:42:44 as usual, provide sufficient error details and name the recipe and layer where it is coming from Sep 02 08:37:18 morning all Sep 02 08:40:50 morning Sep 02 08:42:28 I'm trying to include aubio 0.3.2 in my build, and it requires FFTW3 lib, so I added that too. but now aubio do_configure fails on pkg-config step, since it "can't find the package", previuosly it could not even find the fftw3.h header but that's now fixed Sep 02 08:43:42 so it's as if the lib is there, but the aubio do_configure process can't see it Sep 02 08:43:48 any ideas? Sep 02 08:46:50 * xerent_ tickles bluelightning :> Sep 02 08:50:16 xerent_: I don't have any specific idea about the problem but the usual thing is to look at config.log and see the actual test that's being run Sep 02 08:50:29 and/or the configure script Sep 02 08:50:47 and then usually you'll find it's just looking in the wrong place because of how the test is written Sep 02 08:51:53 the log file states "Alternatively, you may set the environment variables FFTWLIB_CFLAGS and FFTWLIB_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details" Sep 02 08:52:17 that might get me past the configure step, but then linking may fail later if it still can't find the actual library Sep 02 08:52:43 worth a try though Sep 02 08:54:26 could be a naming mismatch though, since the package is called "fftw" and not "fftwlib" Sep 02 08:55:13 but if I rename the recipe to fftwlib, it won't build since it can't find fftwlib-3.3.2/COPYING as opposed to fftw-3.3.2/COPYING Sep 02 08:58:20 xerent_: I'm not sure that would make a difference though, it seems unlikely to me that that name would be bleeding into paths or other names that any user of the library would see - unless you've found otherwise? Sep 02 09:02:59 the fftw tarball won't build unless the recipe is named "fftw", I have no idea why. Sep 02 09:03:17 looking at the aubio configure.ac now, but it's all black magic to me. Sep 02 09:03:20 :/ Sep 02 09:08:51 hi everybody Sep 02 09:10:09 can somebody point me, what is the best way to merge newer yocto releases with my distro based on the previous yocto releases? I am specialy interested in the python3 package Sep 02 09:11:14 it shows that simply copying the python/ folder in meta/recipes-devtools leads to several unresolved dependencies Sep 02 09:15:47 hi everybody Sep 02 09:16:53 is there a way in yocto to not have bitbake redo some tasks? Sep 02 09:17:02 how cna I force it to use the existing stamps? Sep 02 09:17:16 problem is that I had a build in which I did some changes to some conf files Sep 02 09:17:23 then I wanted to redo the image Sep 02 09:17:32 but it started to recompile some old package Sep 02 09:17:39 I stopped the build Sep 02 09:17:44 reverted the changes in the conf file Sep 02 09:17:47 and restarted the build Sep 02 09:17:54 but it went back at recompiling th eold package Sep 02 09:18:20 how can I just tell bitbake to reuse the existing stamps and not invalidate them? Sep 02 09:49:01 Am I doing something wrong? "Your version of bblayers.conf has the wrong LCONF_VERSION (has 6, expecting 7)." Sep 02 09:50:23 bumped local one to 7, just cause. And running bitbake again. It seems to be doing stuff now. Sep 02 09:50:38 it's my first time using OE / yocto / bitbake / poky Sep 02 09:51:03 anybody knows anything about my problem??? Sep 02 09:51:27 I asked about 2 hours ago.. Sep 02 09:51:43 my qestion is: I have problem in "do_compile" task of "qt4-x11-free" package. How can I solve this? I have this problem in both Ubuntu & Gentoo. Sep 02 09:52:51 as i said 2hrs ago: as usual, provide sufficient error details and name the recipe and layer where it is coming from Sep 02 10:01:36 LetoThe2nd: sorry, I didnt see your answer. Sep 02 10:02:56 then don't complain ;) Sep 02 10:02:58 LetoThe2nd: It's "qt4-x11-free_4.8.5" Sep 02 10:03:38 & .obj/release-shared/qgl.o: file not recognized: File truncated collect2: error: ld returned 1 exit status make[1]: *** [../../lib/libQtOpenGL.so.4.8.5] Error 1 make[1]: Leaving directory `/home/somaie/Yocto/poky-daisy-11.0.0/build/tmp/work/i586-poky-linux/qt4-x11-free/4.8.5-r0/qt-everywhere-opensource-src-4.8.5/src/opengl' make: *** [sub-opengl-make_default-ordered] Error 2 ERROR: oe_runmake failed WARNING: exit code 1 from a shell co Sep 02 10:05:07 is that plain poky? and if its on daisy, did it work on dora? Sep 02 10:09:24 LetoThe2nd: is it enough? Sep 02 10:12:01 i get the impression you don't actually read what i write. Sep 02 10:12:03 LetoThe2nd: it's poky-daisy-11.0.0. But I run "bitbake qt4-x11-free" in dora branch (on Gentoo) and the same error happened... Sep 02 10:13:45 ok, are there other layers included? Sep 02 10:15:49 LetoThe2nd: these layers included: poky-daisy-11.0.0/meta & poky-daisy-11.0.0/meta-yocto & poky-daisy-11.0.0/meta-yocto-bsp & meta-openembedded/meta-oe Sep 02 10:17:47 can some of you folks point me, how I can add package to the packaging system (ipk) without need to mention it, and therefore included it in the root fs by default? Sep 02 10:18:36 sm_: the feeling in my guts says that there's something fishy with the combination opengl+qemu in your context. i'll kick off a build too, lets see. Sep 02 10:18:57 sodik: does not parse :-) Sep 02 10:19:00 :-( Sep 02 10:20:17 LetoThe2nd: that was reaction to what? :-) Sep 02 10:20:51 sodik: i can't parse what you said. the sentence does not make sense, at least not to me. Sep 02 10:21:25 ok, I'll try it by different way :) Sep 02 10:22:25 I have INSTALLED_PACKAGE variable in my-layer/recipes-core/images/mydistro.bb Sep 02 10:23:09 if I want the package to be included in rootfs I add it to this variable, right? Sep 02 10:23:35 INSTALLED_PACKAGE doesn't sound like the usual way. Sep 02 10:23:45 it's rather IMAGE_INSTALL, usually Sep 02 10:24:15 my apologies, it is the IMAGE_INSTALL Sep 02 10:24:44 yes, so if you want something installed, add it there. Sep 02 10:25:11 so, there are many packages I want to be added to the repository server (ipk in my case) rather to the fs image by default Sep 02 10:25:53 one example is the python or simillar packages, which only end user will install if he/she need it Sep 02 10:26:00 LetoThe2nd: thanks, I'm waiting. Sep 02 10:26:21 sodik: so you want to build packages, but have them not included in some image? Sep 02 10:26:31 sm_: will take some time. Sep 02 10:28:09 LetoThe2nd: exactly, is the variable I'm looking for "CORE_IMAGE_EXTRA_INSTALL" ? Sep 02 10:28:26 sodik: erm.. no. Sep 02 10:28:48 sodik: you'd just do bitbake whateverpackage Sep 02 10:28:56 then its built, but not installed Sep 02 10:29:35 yes I know that, but how can I add the package to the packaging system? Sep 02 10:29:40 note that you need to run bitbake package-index, to update the package feed Sep 02 10:30:05 sodik: that might be what you are missing, no? Sep 02 10:30:12 ndec: probably, yes. Sep 02 10:30:16 ndec: I think this is the information I was looking for Sep 02 10:31:07 thanks guys. going to to test this.. Sep 02 10:33:09 LetoThe2nd: It's Ok. If you find any solution just send it here & I will read it from Channel logs (if I weren't here) Sep 02 10:34:03 sm_: hey, i didn'T say i'll do your error search. i jsut kicked off a build to see if its a general issue, or rather something in your setup ;) Sep 02 10:47:00 LetoThe2nd: :D It's about 2 weeks that I googling for this error, but wasn't successful.. Sep 02 11:04:29 I have another issue/question: when merging with the latest yocto 1.6.1 I've experienced circular dependencies Sep 02 11:05:54 there is a dependency loop, which is related to dpkg-1.17.4.bb Sep 02 11:06:29 ERROR: Dependency loop #1 found: Task 135 (virtual:native:/data/projects/tetd/212-myrmica-2.0/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb, do_install) (dependent Tasks ['dpkg, do_compile']) Task 136 (virtual:native:/data/projects/tetd/212-myrmica-2.0/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb, do_populate_sysroot) (dependent Tasks ['dpkg, do_install']) Task 138 (virtual:native:/data/projects/tetd/212-myrmica-2.0/meta/recipes-devtools Sep 02 11:06:43 any ideas please? Sep 02 11:16:51 it looks to me that the dependencies are in the same layer. the meta/ and bitbake/ was upgraded from the official yocto git -b daisy Sep 02 11:23:56 so what for do I need the dpkg package anyways? Sep 02 11:31:43 so there is no way to force the build not to invalidate a task? Sep 02 11:33:44 no, it always fail on the dependency loop - just after parsing all recipes Sep 02 11:36:23 so many questions Sep 02 11:36:30 sodik, sorry I was asking for a different problem :) Sep 02 11:36:37 actually it is only one question Sep 02 11:36:59 gebreselaisi: no problem :) Sep 02 11:37:52 xerent_: the question is why is it failing on dependency loop, and how to solve it Sep 02 11:38:33 I cannot see any clue in the error log Sep 02 11:39:12 I have no clue either, I'm stuck with my own issue with pkg-config not finding a previously installed package Sep 02 11:41:01 xerent_, do you see the .pc in sysroot? Sep 02 11:46:37 I'm looking, which folder should it be in? Sep 02 11:46:53 I'm in the sysroot looking Sep 02 11:48:06 it's in tmp/sysroots/{machine_name} Sep 02 11:48:12 that is the sysroot for your machine Sep 02 11:48:24 and in there it should be in the standard location for .pc file Sep 02 11:48:29 usr/lib/pkgconfig Sep 02 11:49:28 if you do not have it there, then your previusly installed package should have it's .pc file in the -dev package Sep 02 11:49:40 there's the fftw3l.pc file yes Sep 02 11:49:59 I need to check in the other configure script exactly which version it's looking for Sep 02 11:50:05 probably some naming mismatch then Sep 02 11:51:36 it checks for fftw3 and fftw3f, not fftw3l Sep 02 11:51:59 so maybe I'm building that library in the wrong configuration or something Sep 02 11:53:39 xerent_, most likely Sep 02 11:54:22 or maybe you also have the fftw3.pc or fftw3f.pc and libs in your previously installed package, but you are just not installing them Sep 02 11:54:31 check the build directory of your previously installed package Sep 02 11:54:53 I added the package myself so likely no :) Sep 02 11:55:13 I think I know what the problem is, I'm passing the wrong configuration flags when building the library, which adds the extra l Sep 02 11:55:28 then maybe you are not compiling it the way you need it after Sep 02 11:55:32 exactly Sep 02 11:58:33 seems to have solved my problem, thanks gebreselaisi ! Sep 02 12:00:23 xerent_, don't mention it :) Sep 02 12:00:42 I won't, I promise ;) Sep 02 12:01:09 :) Sep 02 12:09:04 update. the dependency loop is caused by the additional layers I used(meta-atmel, meta-mylayer) but somehow the ERROR is propagating as it was in the meta/recipes-devtools/dpkg, anybody has the clue what could be the cause of this fail ? Sep 02 12:14:53 sodik, do you have a dpkg recipe in any of those 2 layers? Sep 02 12:20:02 gebreselaisi: no I dont Sep 02 12:21:22 with previous yocto version I was able to build my distro with those two layers included Sep 02 13:17:33 looks like aubio 0.3.2 has a runtime dependency on packages python and python-gnuplot, of which the first is simple to add and the second non-existant Sep 02 13:37:10 so coming back to my question: how to force the build system to not invalidate a task? Sep 02 13:38:48 beats me :) Sep 02 13:39:51 :) Sep 02 14:03:57 what's the best way to add more stuff to the do_install() step Sep 02 14:04:08 I suppose per default a simple "make install" is performed? Sep 02 14:04:21 but if I override it, the default files are not installed Sep 02 14:04:27 for inherit autotools recipes, yes. Sep 02 14:04:40 then you can do_install_append, for exanple Sep 02 14:04:50 that sounds like what I'm looking for Sep 02 14:13:44 or install_prepend Sep 02 14:13:54 depends on what you want to achieve Sep 02 14:14:40 add additional files to the image, that are produced during build but not included in the package Sep 02 14:15:29 you can us any of them in this case; either install_append() or install_prepend() Sep 02 14:16:11 one is before doing the install (the _prepend one) and the other one is the last step of the install stage (the _append one) Sep 02 14:16:28 I figured as much Sep 02 14:16:48 I love how the simple things are explained and how the complex ones are left as an exercise ;) Sep 02 14:17:07 but I assume that's because you know the solutions to the simple things, but not the complex ;) Sep 02 14:17:34 nah, because we like people to bang their heads against the walls with the complex one :D Sep 02 14:17:53 well, do_install_append() worked fine Sep 02 14:18:01 but it didn't solve my problem anyway Sep 02 14:18:12 which is? Sep 02 14:18:46 I built aubio-0.3.2 and included it in the image, but when I run the application aubiopitch I get an error message ImportError: No module named aubio.task Sep 02 14:19:00 but that's not a Yocto problem, it's some issue with my package Sep 02 14:20:30 yeah Sep 02 14:24:38 all: I'm still missing the way how to debug the build failure as my recent circular dependency chain Sep 02 14:24:57 I cant see any relelevant informations in the error log Sep 02 14:25:52 the error is described by build system as problem of one particular package, in that case the dpkg Sep 02 14:26:51 but it is connected with other layers, however the way it is connected is not obvious from the log Sep 02 15:00:56 sigh, bitbake still freaks out when trying to ^C it half the time Sep 02 15:01:13 bad file descriptor, timeouts communicating with bitbake server, etc Sep 02 15:01:19 just from a signel ^C during parsing Sep 02 15:24:56 * kergoth kicks bitbake repeatedly and goes back to using pkill -f to exit it Sep 02 15:31:07 bitbake bites back Sep 02 15:33:05 its true Sep 02 16:06:38 I get a "no package provides" when doing the rootfs for a package Sep 02 16:07:06 even though in the recipe of the failing package I have a RDEPNDS += on the package that provides the lib the build system is complaining about Sep 02 16:07:12 anybody know why is that? Sep 02 16:09:41 altough I see know that the spec file of the package I expected to provide that library, does not list the library in Provides Sep 02 16:09:55 how can I make it to "Provide" a library? Sep 02 16:10:19 you need to be more specific. these generic questions are not something we can answer without more information Sep 02 16:11:30 so Sep 02 16:11:54 I have a package that installs some files which need a library called libEGL.so Sep 02 16:12:18 this means they need a library in the rootfs called libEGL.so Sep 02 16:12:41 on the other hand, I have a package that provides libEGL but in the form of libEGL.so.1.0.0 Sep 02 16:13:16 so I made it that this package also installs the libEGL.so as a symlink, in the ${PN} package, removing it from the -dev package Sep 02 16:13:36 but doing so does not make it to "Provide" libEGL.so Sep 02 16:25:06 question would be Sep 02 16:25:20 can I force a package to "Provide" a symlink? Sep 02 16:27:07 you don't need the symlink in the main package for it to provide the lib Sep 02 16:27:13 its completely unnecessar Sep 02 16:27:23 that symlink is only used for development, not runtime Sep 02 16:27:44 well, I have another package that seems to need libEGL.so Sep 02 16:27:52 not libEGL.so.1 Sep 02 16:28:05 or even the library itself libEGL.so.1.0.0 Sep 02 16:28:26 so I need to have in the rootfs libEGL.so Sep 02 16:28:36 not just in the -dev file Sep 02 16:28:59 I need to register my package as a shlib provider for libEGL.so also Sep 02 16:29:37 no, that's incorrect Sep 02 16:30:34 how would it be correct then? Sep 02 16:32:04 exactly what makes you think the other package needs libEGL.so? Sep 02 16:32:55 because the other package contains a library called libEGL.so, not a symlink, an actual library, that is erased during to install so that another libEGL is used from my new package Sep 02 16:34:14 okay, then your new package needs to hcange how the library is linked so its SONAME matches the other binary's expectations Sep 02 16:34:33 or better yet, chang ethe first package to version the library properly and thereby give it an SONAME other than libEGL.so Sep 02 16:34:34 externalsrc for recipes using SRCPV seems to have issues calculating SRCPV Sep 02 16:34:39 is that known ? Sep 02 16:34:49 or something I am missing Sep 02 16:35:05 the first package is binaries only; nothing is compiled Sep 02 16:56:14 any pointers on how I can get my new library to have it's dlname as libEGL.so instead of libEGL.so.1.0 ? Sep 02 16:56:59 1) why on earth would you want to do that 2) if you're using libtool, -noversion iirc Sep 02 16:57:15 i always get that wrong. -avoid-version. Sep 02 16:57:24 rburton, because I have a recipe that installs some binaries that need libEGL.so Sep 02 16:58:09 gebreselaisi: dynamaically loading i presume. ship the symlink? Sep 02 16:59:11 rburton, if I force the recipe to have libEGL.so in the ${PN}, it does not however register my package as a shlid for libEGL.so and it fails at do_rootfs complaining nobody provides libEGL.so Sep 02 16:59:30 that's interesting Sep 02 17:01:36 how to properly ship the symlink? I added it to _${PN} and also did a INSANE_SKIP_${PN} += "dev-so" to get rid of the QA errors Sep 02 17:01:42 is there another way of doing it? Sep 02 17:08:35 gebreselaisi: that's it Sep 02 17:09:13 gebreselaisi: of course a better solution is to fix the software that loads unversioned libraries Sep 02 17:09:18 because its doing it wrong Sep 02 17:09:31 rburton, those I have in binary form Sep 02 17:09:40 can't do anything about it Sep 02 17:09:46 file a moany bug then Sep 02 17:10:00 time is not on my side :) Sep 02 17:10:17 you'll note that eg debian's libegl doesn't ship a libEGL.so: https://packages.debian.org/sid/amd64/libegl1-mesa/filelist Sep 02 17:12:17 it's been driivng me crazy Sep 02 17:12:56 closed source software: doing it wrong since 1998 Sep 02 17:13:38 so any idea why shipping the symlink fails for me? Sep 02 17:16:16 i already told you, shipping teh symlink won't solve your poroblem Sep 02 17:16:26 you need to change the soname of the lib being linked to match up with the expectations of the binary that wants it Sep 02 17:17:02 so how do I change the soname of the lib? configure.ac looks awfully skinny Sep 02 17:26:22 if the app is dlopening libegl.so then shipping the symlink will work Sep 02 17:26:57 if its a rootfs time/dependency thing then pass -avoid-version to whatever builds libegl.so, assuming it uses libtool. Sep 02 17:36:19 rburton, thanks -avoid-version added to Makefile.am seems to be doing the trick Sep 02 19:04:36 RP: thoughts on setting up a progress bar in the bitbake UI for the setscene callbacks, so we get some indication of progress during sstate fetches? Sep 02 19:04:50 a from scratch full sstate fetch for eg. coore-image-base over http can make it seem like bitbake has hung Sep 02 19:17:23 kergoth: We probably should do something... Sep 02 19:18:22 I'm familiar with what's going on, and even I thought it hung once since I forgot I had set up to use an internal http sstate mirror :) Sep 02 19:18:36 "Why does it keep hanging at runqueue generation??" .... *slaps forehead* Sep 02 19:22:06 kergoth: I agreed its bad from the user perspective Sep 02 19:42:21 halstead: is there any reason that centos7-a and centos7 disappeared? Sep 02 19:58:21 Hi there! I'm having a problem with build host specific include paths showing up in a build. Sep 02 19:58:49 I think it might be due to a BBCLASSEXTEND in popt, but I'm a bit confused in the difference between native and nativesdk. Sep 02 19:59:36 Is it kosher to have "native nativesdk" ? Sep 02 20:02:30 http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-BBCLASSEXTEND Sep 02 20:03:15 This tells me that having both of these is okay, but I can see that autoconf is getting bad info from libpopt when trying to build my recipe (for gphoto2). Sep 02 20:04:17 The following shows up in the gphoto2 Makefile: Sep 02 20:04:23 LIBGPHOTO2_CFLAGS = -I/home/jpl/dev/q7/yocto/poky/build/tmp/sysroots/q7-base/usr/include/gphoto2 Sep 02 20:04:28 POPT_CFLAGS = -I/usr/include Sep 02 20:04:54 The build hits a point where it is trying to pull include files from the workstation instead of sysroot. Sep 02 21:39:55 hi all Sep 02 21:41:20 i recently got a Wandboard Quad and struggled to find an image that provides me with a stable sound and an desktop environment, so now i decided to build my own... Sep 02 21:42:12 unfortunately the core-image-minimal build already fails because it can't build 'quilt', and the log it refers me too states exactly the same as the console output: that a task failed Sep 02 21:42:33 ERROR: Function failed: autotools_preconfigure (log file is located at /media/jan/Storage/yocto/tmp/work/x86_64-linux/quilt-native/0.61-r0/temp/log.do_configure.9848) Sep 02 21:43:32 i'm not sure if i suddenly lost the ability to read logs, but that isn't very helpful ;) Sep 02 21:43:58 btw, that's the error message and the log content (minus a couple of debug lines) Sep 02 21:52:23 guys why don't get any output to xrandr? Sep 02 21:52:33 edm-fairy-imx6:~# xrandr Sep 02 21:52:33 xrandr: Failed to get size of gamma for output default Sep 02 21:52:33 Screen 0: minimum 1024 x 600, current 1024 x 600, maximum 1024 x 600 Sep 02 21:52:33 default connected 1024x600+0+0 0mm x 0mm Sep 02 21:52:33 1024x600 61.0* Sep 02 21:53:56 yocto 1.5.3 Sep 02 21:56:44 censor: anything obviously wrong in log.do_configure or run.autotools_preconfigure? Sep 02 21:57:45 mmm no the building went fine no error in log.do_configure Sep 02 21:57:59 censor: by the way, I'm looking at my build and I have quilt-native 0.63 Sep 02 21:58:15 ant__: log.do_configure contains exactly that message, and run.autotools_preconfigure is just loads of variables and the function Sep 02 21:58:53 can i somehow manually start the build in there? Sep 02 22:01:09 if i go into that folder and run: bash -x temp/run.autotools_preconfigure.10573 Sep 02 22:01:18 it exits with 0 Sep 02 22:02:45 see, these are my logs Sep 02 22:02:52 http://pastebin.com/5VgXJQWG Sep 02 22:02:59 http://pastebin.com/zuELRHKG Sep 02 22:05:10 these are mine: http://paste.ubuntu.com/8218594/ & http://paste.ubuntu.com/8218591/ Sep 02 22:07:51 pls paste log.do_configure.10573 Sep 02 22:08:25 that _is_ log.do_configure.10573 ;-) Sep 02 22:08:51 that's why i meant, the log is identical to the error message, which isn't very helpful :D Sep 02 22:17:54 what is your buildhost OS? Fedora? Sep 02 22:18:03 Ubuntu 14.04 Sep 02 22:18:21 well, like here Sep 02 22:18:50 there are some patches after 0.61 Sep 02 22:18:53 i followed this guide: http://wiki.wandboard.org/index.php/Getting_started_with_Yocto_on_Wandboard Sep 02 22:19:01 can you try tu pull master? Sep 02 22:19:04 should i switch to master? Sep 02 22:19:08 okay Sep 02 22:19:09 http://cgit.openembedded.org/openembedded-core/log/?qt=grep&q=quilt Sep 02 22:23:23 ah, that looks good, thanks =) Sep 02 22:24:00 damn, same error with quilt 0.63 Sep 02 22:24:38 btw, are you using bash or dash? could that be an issue? somebody recommended switching to dash Sep 02 22:24:48 etr, to bash Sep 02 22:26:54 hm... Sep 02 22:26:56 echo $SHELL Sep 02 22:26:56 /bin/bash Sep 02 22:27:43 doh..standard Ubuntu 14.04 LTS Sep 02 22:30:18 bandwidth is cheap, let's start from scratch Sep 02 22:30:50 btw, i think Dash is standard Sep 02 22:31:44 lrwxrwxrwx 1 root root 4 apr 21 21:49 sh -> dash Sep 02 22:32:12 I'm still new with Ubuntu..don't remember having reconfigured Sep 02 22:32:18 just found out that it's the default for scripts, but shell's still use bash Sep 02 22:32:33 * ant__ -> Gentoo lover Sep 02 22:32:42 * censor <3 Debian ;-) Sep 02 22:32:59 but for desktop i prefer Ubuntu then Sep 02 22:35:57 alright, wiped everything, but quilt still craps out Sep 02 22:37:42 then must be one layer poisoning things Sep 02 22:38:13 could be the freescale stuff, i'll try without them Sep 02 22:38:32 or are you out of space ? Sep 02 22:38:41 really, that's weird Sep 02 22:39:07 nah, that storage partition is a 2TB RAID Sep 02 22:43:23 hmm, i think the issue was that the RAID was mounted with 'noexec' Sep 02 22:43:41 so your pointer regarding the fs wasn't off by much ;-) Sep 02 22:54:34 argh... Sep 02 23:01:18 censor, I was about to ask you to fsck ;) Sep 02 23:01:26 good nite Sep 03 01:38:00 i just gave Toaster a quick look, and i can't create a new project because 'Yocto Project version' is empty Sep 03 01:38:20 is that because i'm on master and not a release? if so, how can i fix that? **** ENDING LOGGING AT Wed Sep 03 02:59:59 2014