From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] go: bump to 1.10
Date: Tue, 01 May 2018 16:56:14 -0400 [thread overview]
Message-ID: <87sh7b2iz5.fsf@paral.in> (raw)
In-Reply-To: <87a7tjf8dr.fsf@dell.be.48ers.dk>
Hi Peter,
Peter Korsgaard <peter@korsgaard.com> writes:
> 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.
Agreed, but it's maybe worth noting that I'm successfully compiling on
amd64 targeting arm and arm64.
Best,
Christian
next prev parent reply other threads:[~2018-05-01 20:56 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
2018-05-01 20:56 ` Christian Stewart [this message]
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=87sh7b2iz5.fsf@paral.in \
--to=christian@paral.in \
--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