public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] go: Add recipes for golang compilers and tools
Date: Mon, 12 Dec 2016 10:02:36 -0800	[thread overview]
Message-ID: <F7334516-0C0C-4709-88ED-8FAB7FFA5548@gmail.com> (raw)
In-Reply-To: <a186e3be-242a-5ba1-36fe-f5f3d561552c@mlbassoc.com>

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]


> On Dec 12, 2016, at 4:36 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> 
> Looking at these recipes and they seem like a good starting point.
> I did have some issues though:
> 
> * bitbake go - didn't create any target installable packages, although the
>  .../image directory seemed to be well populated.

Yeah mostly, I was concentrating on cross builds but this is something to look at.

> * bitbake go-helloworld - had these errors:
> ERROR: go-helloworld-0.1-r0 do_populate_lic: QA Issue: go-helloworld: LIC_FILES_CHKSUM points to an invalid file: /MIT [license-checksum]

Thats new, somehow it did not happen for me. I will check again.

> ERROR: go-helloworld-0.1-r0 do_compile: Function failed: do_compile (log file is located at /build/p0382_2016-01-13/tmp/work/cortexa9hf-neon-amltd-linux-gnueabi/go-helloworld/0.1-r0/temp/log.do_compile.31170)
> ERROR: Logfile of failure stored in: /build/p0382_2016-01-13/tmp/work/cortexa9hf-neon-amltd-linux-gnueabi/go-helloworld/0.1-r0/temp/log.do_compile.31170
> Log data follows:
> | DEBUG: Executing shell function do_compile
> | stat helloworld.go: no such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at /build/p0382_2016-01-13/tmp/work/cortexa9hf-neon-amltd-linux-gnueabi/go-helloworld/0.1-r0/temp/log.do_compile.31170)
> ERROR: Task (/local/poky-cutting-edge/meta/recipes-extended/go-examples/go-helloworld_0.1.bb:do_compile) failed with exit code '1'
> 
> I forced the compiler to my target (rsync is _my_ friend) and was
> able to run 'helloword.go'.  I've not tested much past this point,
> but I am enthusiastic about getting 'go' into OE-core


Thanks Gary for your feedback it will help. I know I have a rev2 due for this patchset. Haven’t yet includes all needed changes for v2.

[-- Attachment #2: Type: text/html, Size: 14874 bytes --]

  reply	other threads:[~2016-12-12 18:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  0:39 [PATCH 1/2] go: Add recipes for golang compilers and tools Khem Raj
2016-11-10  0:39 ` [PATCH 2/2] go-examples: Add an example, helloworld written in go Khem Raj
2016-11-11  2:59   ` Christopher Larson
2016-11-14  2:07     ` Khem Raj
2016-11-11 13:10 ` [PATCH 1/2] go: Add recipes for golang compilers and tools Alexander Kanavin
2016-11-11 16:02   ` Khem Raj
2016-11-11 16:44     ` Bruce Ashfield
2016-11-11 16:52     ` Burton, Ross
2016-11-11 18:04   ` Richard Purdie
2016-11-14 13:00     ` Alexander Kanavin
2016-11-14 17:49       ` Khem Raj
2016-11-15 18:43     ` Matt Madison
2016-11-11 17:16 ` Maciej Borzęcki
2016-11-11 18:11   ` Khem Raj
2016-12-12 12:36 ` Gary Thomas
2016-12-12 18:02   ` Khem Raj [this message]
2017-01-25 19:40     ` Maciej Borzęcki
2017-01-25 19:57       ` Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F7334516-0C0C-4709-88ED-8FAB7FFA5548@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox