From: Stanley Lieber <sl@9front.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Making available a pre-compiled go binary for Miller's plan-9 Pi image (Chris McGee)
Date: Sun, 30 Oct 2016 21:47:22 -0400 [thread overview]
Message-ID: <8cf8a0d6-364a-4959-abd0-c47cf87dfdce@email.android.com> (raw)
In-Reply-To: <9155087B-950C-49A0-BE77-B364B2FACF43@gmail.com>
Chris McGee <newton688@gmail.com> wrote:
>I tried this command with both go 1.7.3 and master branches. Both fail
>right after “#### Building packages and commands for host, plan9/386”
>with an error “install: ./install not found.”
>
>It seems like the go bootstrap tool is trying to call a binary called
>“install” but there are none on my system. Is there such a command on
>p9bl? Maybe 9front doesn’t have it?
>
>It works fine if I don’t try to cross compile to plan9/arm or even
>linux/386.
>
>Chris
>
>> On Oct 30, 2016, at 4:39 AM, David du Colombier <0intro@gmail.com>
>wrote:
>>
>> > To cross compile with make.rc do you just set GOARCH and GOOS and
>just run it?
>>
>> Yes and you can add the --no-rebuild flag to prevent cmd/dist to
>remove the existing binaries.
>>
>> For example:
>>
>> ℅ GOOS=plan9 GOARCH=arm make.rc --no-rebuild
>>
>> --
>> David du Colombier
>>
'install' is from BSD. It does not exist in Plan 9.
sl
next prev parent reply other threads:[~2016-10-31 1:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 19:31 Marshall Conover
2016-10-28 20:14 ` David du Colombier
2016-10-29 12:49 ` Chris McGee
2016-10-29 18:46 ` David du Colombier
2016-10-30 2:13 ` Chris McGee
2016-10-30 8:39 ` David du Colombier
2016-10-31 1:08 ` Chris McGee
2016-10-31 1:47 ` Stanley Lieber [this message]
2016-11-01 13:05 ` Chris McGee
2016-11-13 18:07 ` David du Colombier
2016-11-13 18:26 ` Chris McGee
2016-11-13 18:49 ` David du Colombier
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=8cf8a0d6-364a-4959-abd0-c47cf87dfdce@email.android.com \
--to=sl@9front.org \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).