**** BEGIN LOGGING AT Fri Jun 27 02:59:59 2014
Jun 27 07:25:15 <[Sno]> is there a sane way to choose the hardfp variant from gpu-viv-bin-mx6q?
Jun 27 07:51:28 <mckoan> good morning
Jun 27 08:49:34 <Rick__> Hi, how can i tell where my ./configure is located in my recipe during do_configure?
Jun 27 08:49:48 <Rick__> configuring fails: ./configure not found
Jun 27 09:00:52 <[Sno]> Rick__: seems to be in ${S}
Jun 27 09:08:17 <Rick__> [Sno]: I havent modified it in my recipe
Jun 27 09:08:48 <[Sno]> Rick__: I currently dig in xbmc for errors and I see that he's invoking ${S}/configure
Jun 27 09:08:52 <[Sno]> suggest you try it
Jun 27 09:09:14 <[Sno]> S="${WORKDIR}/git" there
Jun 27 09:13:49 <Rick__> same error
Jun 27 09:14:30 <Rick__> source is a loacally stored file in projectdir/files
Jun 27 09:14:37 <Rick__> .tar.gz
Jun 27 09:17:58 <Rick__> [Sno]: SRC_URI="file://proj.tar.gz"
Jun 27 09:18:34 <[Sno]> Rick__: you have to extract it before you can run configure
Jun 27 09:18:58 <[Sno]> so you're S should be ${WORKDIR}/files ?
Jun 27 09:19:39 <Rick__> might be, WORKDIR= where the .BB file is stored?
Jun 27 09:20:42 <Rick__> [Sno]: I tried the same with preunpacked
Jun 27 09:20:56 <ant_work> normally S = "${WORKDIR}/${BP}"
Jun 27 09:21:08 <ant_work> check this before
Jun 27 09:21:08 <[Sno]> Rick__: workdir is somewhere below your builddir
Jun 27 09:21:30 <ant_work> second option, your source doesn't build with S != B
Jun 27 09:21:32 <[Sno]> $builddir/tmp/work/machine-triple/pkg-name/...
Jun 27 09:21:33 <ant_work> maybe
Jun 27 09:22:19 <ant_work> in that case,inherit autoconf-brokensep to verify and possibly fix the sources
Jun 27 09:27:09 <Rick__> it works, i looked further into the logs, and realized the S path was not right
Jun 27 09:30:41 <[Sno]> does anyone has experience in digging ffmpeg's config.log for an error?
Jun 27 09:31:12 <[Sno]> I get xbmc configure error pointing into ffmpeg's log - and it looks not that wrong to me
Jun 27 12:22:18 <Rick__> What does this error mean? QA issur: crchitecture did not match?
Jun 27 12:35:38 <zecke> Rick__: well, the binary/executable that is ending up in the package does notmatch the architecture you are building for
Jun 27 12:35:47 <zecke> Rick__: e.g. the application was not cross compiled
Jun 27 12:58:09 <Rick__> zecke: im trying to cross compile ffmpeg, i tried to configure with --enable-cross-compile arch=arm target-os=linux but i get cant create binary
Jun 27 13:42:34 <[Sno]> what does "Files/directories were installed but not shipped" mean?
Jun 27 13:53:46 <auke-> i'm trying to build irssi from meta-oe, but it fails with errors like "terminfo-core.c:343: undefined reference to `tputs'". It the recipe missing a dependency?
Jun 27 14:32:53 <fabiench> [Sno]: usually it means you didn't add the files or directory you want to deploy to the FILES_${PN} variable
Jun 27 15:15:35 <[Sno]> I recognized - during "debugging" I removed the --prefix option in xbmc
Jun 27 15:15:53 <[Sno]> but the added files were below /imx6/xbmc :)
Jun 27 15:15:59 <[Sno]> so - pebcak :D
Jun 27 15:29:03 <thaytan> I have an image where they want openssh server installed, but don't want it autostarted
Jun 27 15:29:44 <mebrown> Anybody doing embedded with btrfs filesystem? I would like to create a rootfs image with btrfs filesystem, but I cannot see how to enable compression on a mkfs.btrfs call.
Jun 27 15:29:48 <thaytan> what's a good way to leave off installing rc.d links?
Jun 27 15:30:32 <mebrown> thaytan, I just add a function to IMAGE_CMD to remove them.
Jun 27 15:31:21 <thaytan> yeah, I was thinking of a rootfs postprocess cmd
Jun 27 15:31:48 <thaytan> there doesn't seem a good way to avoid them being set up in the first place in a bbappend
Jun 27 15:37:11 <volker-> does someone use disk encryption with yocto?
Jun 27 15:37:14 <kergoth> the update-rc.d bbclass obeys variables, presumably you could just override those variables, unless it's not using update-rc.d, in which case it should be fixed to do so
Jun 27 16:06:23 <thaytan> kergoth, I couldn't see any sensible setting of variables to disable the behaviour
Jun 27 16:06:35 <thaytan> anyway, I'll just postprocess the rootfs
Jun 27 16:07:10 <thaytan> It looks like I'll also need to kill the package's postinst in the image too, or they'll just get installed again at first boot
Jun 27 16:07:27 <thaytan> why is there a postinst when the image already seems to have the right links?
Jun 27 16:07:37 <kergoth> postinsts are run at do_rootfs time
Jun 27 16:07:44 <kergoth> only ones that fail or can't be run there will be run on first boot
Jun 27 16:07:51 <thaytan> ahr
Jun 27 16:10:25 <thaytan> OK, I see - it checks the status of each package
Jun 27 16:10:57 <kergoth> and the postinst can check the value of the D variable, if it's set, its the path to the rootfs at image construction time
Jun 27 16:11:04 <kergoth> if it wants to opt-out of running in that context
Jun 27 16:12:34 <thaytan> thanks :)
Jun 27 16:13:04 <kergoth> np
Jun 27 16:23:09 <kergoth> good god, meta-fsl-ppc's kernel recipe has: COMPATIBLE_MACHINE_$MACHINE = "$MACHINE"
Jun 27 16:23:11 * kergoth twitches
Jun 27 21:11:23 <RP> kergoth: I think a few layers have that kind of construct since it allows them to stack :/
Jun 27 21:13:29 <volker-> is there a way to say "build package X, don't install it to the image but add the package itself to the image at place Y"
Jun 27 21:14:16 <volker-> reason is to have the package installed to an encrypted folder on first boot
Jun 28 01:13:17 <blloyd> are there any other network managers supported by yocto besides connman?  connman keeps getting stuck in a pretty tight infinite loop filling the syslog with {add} {del} events.  And totally killing performance while doing so.
**** ENDING LOGGING AT Sat Jun 28 02:59:58 2014