From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom installation fails due to missing files
Date: Sat, 6 Jul 2013 17:36:38 -0400 [thread overview]
Message-ID: <87a427b2eb8426a5177486e96154120a@lyons.quanstro.net> (raw)
In-Reply-To: <20130706161457.vkkggcET0AcKz2rs+KQM+Q5R@dietcurd.local>
> But then, unfortunately, there were quite some copy errors which
> caused the installation to fail.
>
> /n/[newfs - dist]/68020/lib/{ape,libc.a}
> /n/[newfs - dist]/alpha/lib/{ape,libc.a}
> /n/newfs/sys/src/pcpae/{archacpi,audioac97{,m},audiohd}.c
> (because /n/newfs/sys/src/pcpae doesn't exist)
that's unfortunate. but those files aren't required.
> P.S.: Does the Plan9/9atom awk(1) has the same bug that i ran into
> this week? It is present in all awk(1)s i've tested, including
> GNU awk(1) ($TAWK is simply awk, and UnicodeData.txt is 6.2.0):
the one true awk (bwk's source) does not accept hex, so it doesn't
have this bug.
on 9atom, /sys/src/cmd/runetype has the files used to automaticly
generate /lib/unicode, the unicode tables used by libc, and an awk
version of /sys/src/cmd/aux/mklatinkbd.c (not used). there is also
the source for the programs in rune(1),
http://www.9atom.org/magic/man2html/1/rune
- erik
next prev parent reply other threads:[~2013-07-06 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 15:14 Steffen Daode Nurpmeso
2013-07-06 21:36 ` erik quanstrom [this message]
2013-07-08 12:06 ` Steffen Daode Nurpmeso
2013-07-08 12:42 ` Carl Phillips
2013-07-08 13:28 ` Steffen Daode Nurpmeso
2013-07-08 13:32 ` erik quanstrom
2013-07-08 14:51 ` Carl Phillips
2013-07-17 18:06 ` erik quanstrom
2013-07-18 10:28 ` Steffen Daode Nurpmeso
2013-07-08 19:55 ` [9fans] 9atom installation fails due to missing files [solved] Steffen Daode Nurpmeso
2013-07-08 20:06 ` Matthew Veety
2013-07-08 20:53 ` Steffen Nurpmeso
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=87a427b2eb8426a5177486e96154120a@lyons.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).