From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Python/Mercurial error
Date: Fri, 4 Apr 2014 16:23:44 +0530 [thread overview]
Message-ID: <CAA6Yd9UYbbo63C+Ow6EQ5c319P=btGc15pG=eyZbq=G0t-o7fg@mail.gmail.com> (raw)
In-Reply-To: <20140402071913.72076a71@zinc.9fans.fr>
On Wed, Apr 2, 2014 at 10:49 AM, David du Colombier <0intro@gmail.com> wrote:
> Two days ago, I've fixed the script mklibc.rc to
> generate the libc_plan9.h file properly on 9atom.
>
> https://codereview.appspot.com/82660044/
>
> Please give a try and review this change to
> get it submitted before the Go 1.4 release.
I got a fresh copy of go from the current hg tip and applied this
patch. I now see some other errors while it builds pkg/math module: I
had not seen these before, so perhaps something new that landed in the
go repo may be responsible for it?
go/src/pkg/math/abs.go:14: internal error: abs ~r1 (type float64)
recorded as live on entry
[...] same error for various other files (acosh.go, asin.go ... )
[...]
go tool dist: FAILED: ...
It will be great if one of the "distributions" like 9atom ship a
version of various tools like hg/python/go along with it.
--
Ramakrishnan
next prev parent reply other threads:[~2014-04-04 10:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:59 Ramakrishnan Muthukrishnan
2014-03-26 7:35 ` David du Colombier
2014-03-26 11:09 ` Ramakrishnan Muthukrishnan
2014-03-26 11:53 ` peterhull90
2014-03-26 12:08 ` Ramakrishnan Muthukrishnan
2014-03-26 13:50 ` erik quanstrom
2014-04-02 5:19 ` David du Colombier
2014-04-02 5:40 ` David du Colombier
2014-04-02 7:29 ` kokamoto
2014-04-03 5:12 ` kokamoto
2014-04-03 6:00 ` David du Colombier
2014-04-03 6:04 ` erik quanstrom
2014-04-02 12:48 ` erik quanstrom
2014-04-03 5:50 ` David du Colombier
2014-04-03 5:58 ` erik quanstrom
2014-04-03 6:15 ` Jeff Sickel
2014-04-03 6:20 ` David du Colombier
2014-04-03 6:24 ` erik quanstrom
2014-04-03 17:18 ` Ramakrishnan Muthukrishnan
2014-04-03 17:21 ` erik quanstrom
2014-04-03 17:57 ` David du Colombier
2014-04-03 18:01 ` erik quanstrom
2014-04-03 18:23 ` David du Colombier
2014-04-04 1:09 ` Ramakrishnan Muthukrishnan
2014-04-04 1:15 ` erik quanstrom
2014-04-03 18:04 ` Ramakrishnan Muthukrishnan
2014-04-03 19:21 ` David du Colombier
2014-04-04 5:39 ` Jeff Sickel
2014-04-07 18:27 ` Ramakrishnan Muthukrishnan
2014-04-04 10:53 ` Ramakrishnan Muthukrishnan [this message]
2014-04-04 11:38 ` David du Colombier
2014-03-26 12:09 ` Mark van Atten
2014-03-26 12:38 ` David du Colombier
2014-03-26 13:23 ` Ramakrishnan Muthukrishnan
2014-03-31 5:44 ` kokamoto
2014-03-31 6:23 ` David du Colombier
2014-03-31 6:47 ` kokamoto
2014-03-31 13:00 ` erik quanstrom
2014-04-01 0:57 ` kokamoto
2014-04-01 1:03 ` erik quanstrom
2014-04-01 2:27 ` kokamoto
2014-04-01 3:05 ` erik quanstrom
2014-04-01 6:46 ` kokamoto
2014-04-01 13:54 ` erik quanstrom
2014-04-02 2:54 ` kokamoto
2014-04-02 5:10 ` David du Colombier
2014-04-02 6:20 ` kokamoto
2014-03-26 13:47 ` erik quanstrom
2014-03-26 14:13 ` David du Colombier
2014-03-26 14:19 ` Ramakrishnan Muthukrishnan
2014-03-26 13:24 ` Ramakrishnan Muthukrishnan
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='CAA6Yd9UYbbo63C+Ow6EQ5c319P=btGc15pG=eyZbq=G0t-o7fg@mail.gmail.com' \
--to=vu3rdd@gmail.com \
--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).