9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] runebase breaking libs build
Date: Mon, 19 Jan 2015 08:52:25 +0100	[thread overview]
Message-ID: <20150119085225.59e49568@zinc.9fans.fr> (raw)
In-Reply-To: <CAL_X0tBnTmXJ-c0pYN2GjU92snANBLho2OS301oVd8JC9JmVLg@mail.gmail.com>

> I upgraded via pull, then `{cd /sys/src/; mk objtype='amd64' install};
> which broke at libc. If the issue is the compilers not being built
> first, maybe it could be documented on the wiki that they need to be
> built first, otherwise odd errors would occur during a world-build.

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

Alternatively, you can simply recompile your amd64
binaries from a 386 machine, since the 386 binaries
on /n/sources are already up-to-date.

--
David du Colombier



  parent reply	other threads:[~2015-01-19  7:52 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 [this message]
2015-01-20  9:35               ` Zbigniew Radosz
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=20150119085225.59e49568@zinc.9fans.fr \
    --to=0intro@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).