Buildroot Archive on 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: Tue, 01 May 2018 22:06:40 +0200	[thread overview]
Message-ID: <87a7tjf8dr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <877eoxc3uq.fsf@paral.in> (Christian Stewart's message of "Mon, 23 Apr 2018 11:57:49 -0400")

>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:

 > Hi Peter,
 > Peter Korsgaard <peter@korsgaard.com> writes:
 >> 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?

 > I haven't had a chance to check on this yet. I'm puzzled why the
 > behavior would be different between glibc and uclibc.

It probably isn't, but if the host uses glibc and the target you build
for also uses glibc (and the same architecture), then it probably works
to link with the target libc instead of the host one.

 > Will do some testing when possible.

Thanks!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-05-01 20:06 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
2018-04-23 15:57     ` Christian Stewart
2018-05-01 20:06       ` Peter Korsgaard [this message]
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=87a7tjf8dr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox