From: Zbigniew Radosz <zbigniew.radosz@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] runebase breaking libs build
Date: Tue, 20 Jan 2015 10:35:20 +0100 [thread overview]
Message-ID: <CAGP-aFxw6Z_JwD9m7hnZHGQMRukdZKO0cnvjZSExPUSYJ=DLnA@mail.gmail.com> (raw)
In-Reply-To: <20150119085225.59e49568@zinc.9fans.fr>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Hi 9fans,
I also attempted to build amd64 version some time ago, and it failed in
libc. I gave up then, but since someone brought this up, let me ask my
question here.
Bell Labs doesn't distribute amd64 binaries. It seems
> you are running a compiler built before the long rune
> change (before May 2013), but the sources are more recent.
>
> In this case, you need to re-bootstrap the compiler,
> as described here:
>
> http://9fans.net/archive/2013/05/81
>
I followed this one and it solves the runebase problem, but libc build
still fails as there is no amd64 subdir in libc. Looks like the labs
version does not have amd64 code for libc. Is that correct? And is libc the
only missing part?
--
Zbigniew Radosz
[-- Attachment #2: Type: text/html, Size: 1141 bytes --]
next prev parent reply other threads:[~2015-01-20 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 23:23 Don Bailey
2015-01-19 4:01 ` erik quanstrom
2015-01-19 4:14 ` Don Bailey
2015-01-19 4:14 ` erik quanstrom
2015-01-19 5:09 ` Don Bailey
2015-01-19 5:16 ` erik quanstrom
2015-01-19 5:40 ` Don Bailey
2015-01-19 5:47 ` erik quanstrom
2015-01-19 7:52 ` David du Colombier
2015-01-20 9:35 ` Zbigniew Radosz [this message]
2015-01-20 9:50 ` David du Colombier
2015-01-20 12:08 ` Zbigniew Radosz
2015-01-20 12:14 ` Quintile
2015-01-20 22:26 ` erik quanstrom
2015-01-21 4:10 ` lucio
2015-01-21 14:11 ` erik quanstrom
2015-01-19 5:50 ` Bakul Shah
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='CAGP-aFxw6Z_JwD9m7hnZHGQMRukdZKO0cnvjZSExPUSYJ=DLnA@mail.gmail.com' \
--to=zbigniew.radosz@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).