From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] easy install of go on 9front?
Date: Wed, 23 Nov 2016 10:57:27 -0500 [thread overview]
Message-ID: <791A1F3F-85EE-4108-9DDB-8AA3689C35E9@stanleylieber.com> (raw)
In-Reply-To: <CAK0pxsGXY3uQn-anPe6PeF9bEnznqJpZ4zrzU90VVUup+OBo1w@mail.gmail.com>
On Nov 23, 2016, at 10:45 AM, Marshall Conover <marzhall.o@gmail.com> wrote:
>
> When I was last working on things a month or so ago, I believe the build problem with building go on 9front was related to mismatched type declarations; that is, certain types were declared in 9front as being uint_32 or the like, and in go being uint_64, or something of that nature. The details have escaped me, but the binaries may be the simplest method, because they're (hopefully) just plug-and-play.
Perform the empirical test. Building on amd64 works fine. Building on 386 is broken since 1.4.3 and now even building 1.4.2 fails. The trivial fixes mentioned have not been verified, documented, nor applied upstream.
The 386 binaries in question suicide on 9front. Fish and others are well aware of this since at least 1.5 but nobody does anything to address the problem. We just tell people who don't know any better that everything works great.
Welcome to the Plan 9 community.
sl
next prev parent reply other threads:[~2016-11-23 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 9:05 Rudolf Sykora
2016-11-23 10:07 ` [9front] " Aram Hăvărneanu
2016-11-23 11:52 ` Marshall Conover
2016-11-23 15:44 ` Stanley Lieber
2016-11-24 2:01 ` kokamoto
2016-11-24 2:26 ` sl
2016-11-23 15:39 ` Stanley Lieber
2016-11-23 15:45 ` Marshall Conover
2016-11-23 15:57 ` Stanley Lieber [this message]
2016-11-23 15:59 ` Marshall Conover
2016-11-24 21:58 ` Matthew Veety
2016-11-23 15:38 ` Stanley Lieber
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=791A1F3F-85EE-4108-9DDB-8AA3689C35E9@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).