I hope we are talking a week or less, but I'm not able to give you a definitive answer - it depends on patch review and how busy we are dealing with issues on the master branch among other things.
Cheers, Paul On Mon, 14 Mar 2016 13:49:40 Steve Rae wrote: > thanks much... > I am very new to this: does "not long though" mean 2-3 days or 2-3 weeks or > ??? > > > On Mon, Mar 14, 2016 at 1:47 PM, Paul Eggleton > > <paul.eggle...@linux.intel.com> wrote: > > Hi Steve, > > > > I've just sent out the patches; beyond that it's a matter of the stable > > branch testing and integration process. I hope not long though. > > > > Cheers, > > Paul > > > > On Mon, 14 Mar 2016 11:51:08 Steve Rae wrote: > >> Paul -- please ETA for getting this into the "jethro" branch. > >> Thanks, Steve > >> > >> On Fri, Mar 11, 2016 at 10:11 AM, Steve Rae <steve....@broadcom.com> wrote: > >> > OK - this seems to build successfully - Thanks! > >> > > >> >>> although I still do see the line: > >> > Cloning into '/tmp/devtool6ZA4IK/workdir/source'... > >> > > >> > On Thu, Mar 10, 2016 at 7:07 PM, Paul Eggleton > >> > > >> > <paul.eggle...@linux.intel.com> wrote: > >> >> On Fri, 11 Mar 2016 07:55:25 Paul Eggleton wrote: > >> >>> On Wed, 09 Mar 2016 10:12:30 Steve Rae wrote: > >> >>> > ( using jethro ) > >> >>> > > >> >>> > I have a 'linux-yocto-custom' layer which builds successfully; then > >> >>> > I > > > > run: > >> >>> > devtool modify -x linux-yocto-custom ../../poky-dev/kernel > >> >>> > >> > >> >>> > >> I see a line: > >> >>> > Cloning into '/tmp/devtoolfgiLXr/workdir/source'... > >> >>> > > >> >>> > Then I run: > >> >>> > devtool build linux-yocto-custom > >> >>> > >> > >> >>> > >> it reports the following: > >> >>> > Log data follows: > >> >>> > | DEBUG: Executing shell function do_kernel_configme > >> >>> > | NOTE: kernel configme > >> >>> > | [INFO] Configuring target/machine combo: "standard/bcmjava" > >> >>> > | [ERROR] frag > >> >>> > > >> >>> > /tmp/devtoolfgiLXr/workdir/source/.meta/cfg/scratch/obj/tmp/devtool > >> >>> > fgi > >> >>> > LXr/ > >> >>> > wo rkdir/defconfig does not exist > >> >>> > > >> >>> > | [ERROR] No configuration fragments found, this typically is a > >> >>> > > >> >>> > misconfigured BSP. > >> >>> > > >> >>> > | Check that fragments (or defconfigs) are referenced by > >> >>> > | the > >> >>> > | board > >> >>> > > >> >>> > description. > >> >>> > > >> >>> > | config of "standard/bcmjava" failed > >> >>> > | WARNING: exit code 1 from a shell command. > >> >>> > > >> >>> > which is true, because "devtool modify -x" deletes the temp > >> >>> > directory > >> >>> > ("/tmp/devtoolfgiLXr") that it used to create this specified > >> >>> > workspace.... > >> >>> > >> >>> Hmm, it looks like the temporary path is leaking in somewhere. Is > >> >>> there > >> >>> an > >> >>> easy way I can reproduce this here so I can debug it? > >> >> > >> >> Actually I just realised, this task ought not to be running at all - > >> >> in > >> >> master we've disabled it under these circumsances. There's also one > >> >> other fix on master that you'd benefit from in jethro - I've put them > >> >> both on this>> > >> >> > >> >> contrib branch: > >> >> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=paule/ > >> >> jet > >> >> hro-fixes4>> > >> >> > >> >> If you could let me know how it works for you that would be great; > >> >> I'll > >> >> send it out soon. > >> >> > >> >> Cheers, > >> >> Paul > >> >> > >> >> -- > >> >> > >> >> Paul Eggleton > >> >> Intel Open Source Technology Centre > > > > -- > > > > Paul Eggleton > > Intel Open Source Technology Centre -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto