From: Quintile <steve@quintile.net>
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 12:14:13 +0000 [thread overview]
Message-ID: <DD105CB0-5F91-4BD4-895F-152671820032@quintile.net> (raw)
In-Reply-To: <CANUoZoH+5zt2Ndp=iuo9MKekH1quRzePfK1k_3+H6iwHf8rynA@mail.gmail.com>
there are a few subdirectories that need to be created when you build the amd64 code for the first time. maybe it would be nice to have a /sys/lib/newobjtype script to help, but if you just:
cd /sys/src
objtype=amd64 mk install
and create the directories as needed you should be ok
-Steve
On 20 Jan 2015, at 09:50, David du Colombier <0intro@gmail.com> wrote:
>> 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?
>
> Yes, some parts of the amd64 user space are missing in
> the Bell Labs distribution. You have you apply these patches:
>
> hget http://9legacy.org/9legacy/patch/amd64.diff | ape/patch -p0
> hget http://9legacy.org/9legacy/patch/amd64-fix.diff | ape/patch -p0
>
> Also, you have to create the sub-directories in /amd64/bin.
>
> You can take a look to my notes available here:
>
> http://9legacy.org/9legacy/doc/nix/usage
>
> --
> David du Colombier
next prev parent reply other threads:[~2015-01-20 12:14 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
2015-01-20 9:50 ` David du Colombier
2015-01-20 12:08 ` Zbigniew Radosz
2015-01-20 12:14 ` Quintile [this message]
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=DD105CB0-5F91-4BD4-895F-152671820032@quintile.net \
--to=steve@quintile.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).