[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    Re: [OE-core] Recipe specific sysroots: New failure to compile Go
From:       Khem Raj <raj.khem () gmail ! com>
Date:       2017-02-28 18:59:53
Message-ID: CAMKF1soHSjdEKaOomKaXfVWqF-xY1h+Cxeuhv5ivNMZV-z02_g () mail ! gmail ! com
[Download RAW message or body]

On Tue, Jan 24, 2017 at 3:34 AM, Kristian Amlie
<kristian.amlie@mender.io> wrote:
> On 24/01/17 11:17, Jussi Kukkonen wrote:
> > On 24 January 2017 at 11:36, Kristian Amlie <kristian.amlie@mender.io
> > <mailto:kristian.amlie@mender.io>> wrote:
> > [snip]
> > 
> > /home/jenkins/workspace/yoctobuild/build-qemu/tmp/work/x86_64-linux/go-native/1.7. \
> > 4-r0/recipe-sysroot-native/usr/lib/go-bootstrap-native-1.4.3/pkg/tool/linux_amd64/6l:
> >  readsym out of sync
> > > WARNING: exit code 2 from a shell command.
> > > ERROR: Function failed: do_compile (log file is located at
> > /home/jenkins/workspace/yoctobuild/build-qemu/tmp/work/x86_64-linux/go-native/1.7.4-r0/temp/log.do_compile.10566)
> >                 
> > ERROR: Task
> > (virtual:native:/home/jenkins/workspace/yoctobuild/oe-meta-go/recipes-devtools/go/go_1.7.4.bb:do_compile)
> >  failed with exit code '1'
> > -----------------------------------------------
> > 
> > Note in particular the "readsym out of sync", which appears to be the
> > heart of the problem.
> > 
> > Using git bisect I have verified that it is the commit
> > 9107d6ca144ac1f6169830dee25dae2dad775333, the introduction of recipe
> > specific sysroots, that breaks the build. However, I cannot see an
> > obvious link between the two, the error looks very internal to Go. Any
> > clue what's going on?
> > 
> > 
> > This could be a symptom of a missing dependency in the go (or
> > go-bootstrap) recipe: the recipe specific sysroot only contains the
> > specified build dependencies unlike the previous system where the
> > sysroot typically contained loads of other things as well.
> 
> Probably. I've been looking at the dependencies for gcc-cross, which
> should be similar, but no luck so far.
> 
did you get to bottom of this issue ?

> --
> Kristian
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


[prev in list] [next in list] [prev in thread] [next in thread]