9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] runebase breaking libs build
Date: Tue, 20 Jan 2015 14:26:12 -0800	[thread overview]
Message-ID: <7a81fdc6f5d8bf97d6fe1c458a9a8cb1@lilly.quanstro.net> (raw)
In-Reply-To: <DD105CB0-5F91-4BD4-895F-152671820032@quintile.net>

On Tue Jan 20 04:10:48 PST 2015, steve@quintile.net wrote:
> 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

objtype=amd64 cd $objtype/bin && mkdir -p ape auth aux bitsy dial disk fossil fs games ip ip/httpd ndb rune opc replica upas venti usb

we don't add arches very often, so i've just created the full set of directories in 9atom.

by the way, the default 9atom install is amd64.  so there's no need to convert.  it will
also build 386 and arm exes at install time, too.

- erik



  reply	other threads:[~2015-01-20 22:26 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
2015-01-20 22:26                     ` erik quanstrom [this message]
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=7a81fdc6f5d8bf97d6fe1c458a9a8cb1@lilly.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).