From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] runebase breaking libs build
Date: Sun, 18 Jan 2015 21:47:44 -0800 [thread overview]
Message-ID: <a4123247f21714d68b0502f5126eb793@brasstown.quanstro.net> (raw)
In-Reply-To: <CAL_X0tBnTmXJ-c0pYN2GjU92snANBLho2OS301oVd8JC9JmVLg@mail.gmail.com>
On Sun Jan 18 21:36:26 PST 2015, don.bailey@gmail.com wrote:
> This will be the last email I send regarding this issue as I have no
> interest in getting into a long drawn-out 9fans-style discussion.
>
> 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.
sorry if that came off snarky. i am however thinking that it's more likely
a build error on sources, or other snafu rather than something that is
a systematic issue.
and assuming that you were running on 386
so there are executables to pull, it sounds like the error
was that the correct executables were not built.
do your 386/6[acl] dates and sums match sources?
do you think that could be it? if so, it sounds like 6[acl] need to rebuilt on
sources.
- erik
next prev parent reply other threads:[~2015-01-19 5:47 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 [this message]
2015-01-19 7:52 ` David du Colombier
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=a4123247f21714d68b0502f5126eb793@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).