**** BEGIN LOGGING AT Mon Apr 20 02:59:58 2015
Apr 20 08:55:29 <ant_work> hi bluelightning
Apr 20 08:55:37 <bluelightning> hi ant_work
Apr 20 08:55:48 <ant_work> still puzzled by the S to set for kexecboot-cfg
Apr 20 08:57:35 <ant_work> I'll spend more time on it this night
Apr 20 09:00:27 <ant_work> that warning just appeared once, on build from scratch
Apr 20 09:00:47 <ant_work> cleaning it from sstate and rebuilding didn't give it out...
Apr 20 09:01:27 <ant_work> I expect the warning to be triggered on each build
Apr 20 09:36:49 <bluelightning> if it's not showing up it indicates that S exists, so for some reason it didn't exist before and now does
Apr 20 11:09:54 <ant_work> the recipe is so simple that bitbake -e doesn't seem giving any interesting output
Apr 20 11:10:15 <ant_work> S is only referenced once
Apr 20 11:10:17 <ant_work> do_configure_prepend () {
Apr 20 11:10:17 <ant_work>     install -m 0644 ${WORKDIR}/icon.xpm ${S}
Apr 20 11:17:35 <bluelightning> for recipes like that you would probably set S = "${WORKDIR}"
Apr 20 11:18:10 <ant_work> I think it was my first try (after seeing similar fixes by lumag)
Apr 20 11:18:22 <ant_work> but it leads to build failure iirc
Apr 20 11:18:45 <bluelightning> what kind of failure?
Apr 20 11:19:41 <ant_work> can't remeber exactly, do_configure or do_build prolly
Apr 20 11:20:31 <ant_work> I'll fire again some tests later on
Apr 20 11:25:36 <ant_work> nope
Apr 20 11:25:49 <ant_work> (wrong windows)
Apr 20 11:31:22 <ant_work> heh, I was chatting with JaMa about his e-mails tagged SPAM by GMail
Apr 20 21:22:38 <ant_home> bluelightning,
Apr 20 21:23:10 <ant_home> so, about kexecboot-cfg
Apr 20 21:25:44 <ant_home> if I set #S = "${WORKDIR}/${BP}"
Apr 20 21:25:45 <ant_home> S = "${WORKDIR}"
Apr 20 21:25:51 <ant_home> I get
Apr 20 21:26:18 <ant_home> | DEBUG: Executing shell function do_configure
Apr 20 21:26:19 <ant_home> | install: '/tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot-cfg/0.2-r0/icon.xpm' and '/tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot-cfg/0.2-r0/icon.xpm' are the same file
Apr 20 21:26:19 <ant_home> | WARNING: exit code 1 from a shell command.
Apr 20 21:26:19 <ant_home> | ERROR: Function failed: do_configure (log file is located at /tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot-cfg/0.2-r0/temp/log.do_configure.6832)
Apr 20 21:27:07 <ant_home> what's more strange, I don't getthe WARNING anymore
Apr 20 21:28:30 <ant_home> with S = "${WORKDIR}/${BP}"
Apr 20 21:29:05 <ant_home> is it inded a race?
Apr 20 21:49:20 <bluelightning> ant_home: er, yeah... well there's an explicit do_configure that tries to copy from ${WORKDIR} to ${S}, of course it fails when those are the same thing...
Apr 20 21:51:42 <ant_home> heh, I get it
Apr 20 21:52:43 <ant_home> but then why did it complain on first build from scratch and not on further rebuilds using S = "${WORKDIR}/${BP}" ?
Apr 20 21:54:11 <ant_home> that dir kexecboot-cfg-0.2 is empty
Apr 20 21:54:12 <bluelightning> I assume because ${WORKDIR}/${BP} didn't get cleared out between builds
Apr 20 21:54:29 <bluelightning> or rather didn't get deleted
Apr 20 21:54:35 <ant_home> hmm
Apr 20 21:54:42 <bluelightning> possibly true for every recipe
Apr 20 21:55:59 <ant_home> after bitbake -c cleansstate kexecboot-cfg
Apr 20 21:56:21 <ant_home> that dir does indeed survive
Apr 20 22:01:21 <ant_home> this is log do_cleansstate
Apr 20 22:01:23 <ant_home> DEBUG: Executing python function do_cleansstate
Apr 20 22:01:23 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg:collie-oe-linux-gnueabi:0.2:r0:collie:3:*_package_write_ipk.tgz*
Apr 20 22:01:23 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg::0.2:r0::3:*_populate_lic.tgz*
Apr 20 22:01:25 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg:collie-oe-linux-gnueabi:0.2:r0:collie:3:*_package.tgz*
Apr 20 22:01:28 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg:collie-oe-linux-gnueabi:0.2:r0:collie:3:*_package_qa.tgz*
Apr 20 22:01:33 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg:collie-oe-linux-gnueabi:0.2:r0:collie:3:*_populate_sysroot.tgz*
Apr 20 22:01:36 <ant_home> NOTE: Removing /oe/oe-core/build/sstate-cache/*/sstate:kexecboot-cfg:collie-oe-linux-gnueabi:0.2:r0:collie:3:*_packagedata.tgz*
Apr 20 22:01:39 <ant_home> DEBUG: Python function do_cleansstate finished
Apr 20 22:01:41 <ant_home> it doesn't remove it
Apr 20 22:02:14 <ant_home> to me it seems a bug
Apr 20 22:11:53 <ant_home> i.e. for kexecboot.bb -c cleansstate removes ${WORKDIR}/${BP}
Apr 20 22:14:40 <ant_home> yes, it is removed on run.base_do_unpack
Apr 20 22:16:24 <ant_home> strange notes there...
Apr 20 22:16:25 <ant_home>     # Ensure that we cleanup /tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot/0.6-r0/kexecboot-0.6/patches
Apr 20 22:16:25 <ant_home>     # TODO: Investigate if we can remove
Apr 20 22:16:25 <ant_home>     # the entire /tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot/0.6-r0/kexecboot-0.6 in this case.
Apr 20 22:16:28 <ant_home>     s_dir = d.getVar('S', True)
Apr 20 22:16:32 <ant_home>     p_dir = os.path.join(s_dir, 'patches')
Apr 20 22:16:34 <ant_home>     bb.utils.remove(p_dir, True)
Apr 20 22:19:11 <ant_home> ah ha
Apr 20 22:19:17 <ant_home> double slash there
Apr 20 22:19:18 <ant_home>     # Ensure that we cleanup /tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot-cfg/0.2-r0/kexecboot-cfg-0.2//patches
Apr 20 22:19:20 <ant_home>     # TODO: Investigate if we can remove
Apr 20 22:19:20 <ant_home>     # the entire /tmp/build/tmp-glibc/work/collie-oe-linux-gnueabi/kexecboot-cfg/0.2-r0/kexecboot-cfg-0.2/ in this case.
Apr 20 22:19:20 <ant_home>     s_dir = d.getVar('S', True)
Apr 20 22:19:21 <ant_home>     p_dir = os.path.join(s_dir, 'patches')
Apr 20 22:19:22 <ant_home>     bb.utils.remove(p_dir, True)
Apr 20 22:20:05 <ant_home> no help from ending slash
Apr 20 22:38:40 <ant_home> okay, at least we know why the warning is only spit once
Apr 20 22:43:53 <ant_home> enough for today
Apr 20 22:43:55 <ant_home> gn
**** ENDING LOGGING AT Tue Apr 21 02:59:58 2015