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

List:       openembedded-core
Subject:    Re: [OE-core] GO runtime crashes
From:       Khem Raj <raj.khem () gmail ! com>
Date:       2019-02-28 18:24:18
Message-ID: CAMKF1sp+Fx-K=1gdVS79zx8-j7ZgcHL12eg1FSgtJ7k2S8QKdA () mail ! gmail ! com
[Download RAW message or body]

On Thu, Feb 28, 2019 at 10:19 AM Damien Riegel <damien.riegel@gmail.com> wrote:
> 
> Hi,
> 
> On Thu, 28 Feb 2019 at 09:04, Vincent Prince
> <vincent.prince.fr@gmail.com> wrote:
> > 
> > Hi Khem,
> > 
> > GO_DYNLINK_x86-64 = "" solution works as well,
> > 
> > Best regards,
> > Vincent
> > 
> > Le jeu. 28 févr. 2019 à 14:14, Khem Raj <raj.khem@gmail.com> a écrit :
> > > 
> > > On Thu, Feb 28, 2019 at 1:35 AM Vincent Prince
> > > <vincent.prince.fr@gmail.com> wrote:
> > > > 
> > > > Hi Damien,
> > > > 
> > > > With GO_LINKSHARED = "" it work fine.
> > > > 
> > > 
> > > Please set
> > > GO_DYNLINK_x86-64 = "1"
> > > to
> > > GO_DYNLINK_x86-64 = ""
> > > in goarch.bbclass
> 
> Well, making a change in the goarch.bbclass is way more intrusive than
> changing the value in a single recipe, so it would be nice to (at least)
> give some justification about this solution.
> 

this will make static binaries instead, so I wonder if its doing some
linking from host.

> > > 
> > > > I'm very new to Go, does it mean that there is a mixing issue in go modules \
> > > > from Yocto and from node_exporter vendor folder, so it links wrongly at \
> > > > runtime?
> 
> As to why the GO_LINKSHARED ="" works, I cannot tell. I just noticed
> that our application was linked differently on my machine (where it
> worked) and in Yocto (where it didn't work), so I tweaked link flags
> until I got it to work.
> 
> Cheers,
> Damien
-- 
_______________________________________________
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]