All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] go: bump to 1.10
Date: Sun, 01 Apr 2018 16:59:15 +0200	[thread overview]
Message-ID: <87y3i7q8fw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87po3js3j3.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 01 Apr 2018 11:02:24 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:
 >> This commit bumps the Go programming language to the 1.10 release.
 >> Signed-off-by: Christian Stewart <christian@paral.in>

 > This causes a number of build issues (strangely enough only from March
 > 13th). Care to take a look?

 > http://autobuild.buildroot.net/?reason=host-go-1.1

Sorry, there actually were earlier failures (going back to Feb 20th, so
right after bumping the version).

What is common for all the failures is that the target arch == host arch
(x86-64) AND the C library is different (musl/uclibc-ng).

I did a quick test here and the reason is that host-go gets linked with
the target C library:

ls -lah build/host-go-1.10/bin/go
-rwxr-xr-x 1 peko peko 11M Apr  1 16:44 build/host-go-1.10/bin/go

./build/host-go-1.10/bin/go
zsh: no such file or directory: ./build/host-go-1.10/bin/go

ldd ./build/host-go-1.10/bin/go
        linux-vdso.so.1 (0x00007ffcd2bae000)
        libc.so.0 => not found

libc.so.0 is uClibc-ng.

Care to take a look?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-04-01 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19  7:27 [Buildroot] [PATCH 1/1] go: bump to 1.10 Christian Stewart
2018-02-19 20:04 ` Peter Korsgaard
2018-04-01  9:02 ` Peter Korsgaard
2018-04-01 14:59   ` Peter Korsgaard [this message]
2018-04-23 15:57     ` Christian Stewart
2018-05-01 20:06       ` Peter Korsgaard
2018-05-01 20:56         ` Christian Stewart
2018-05-02 13:25           ` Peter Korsgaard

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=87y3i7q8fw.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.