From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] 9atom install error
Date: Wed, 25 Jun 2014 23:27:21 -0400 [thread overview]
Message-ID: <681eaf1b4ab51dffe048828421eb9801@ladd.quanstro.net> (raw)
In-Reply-To: <CAA6Yd9VC+qgYWe-H5=b+za4aweyvtcZtMybUD3T5O3SuhS7=kg@mail.gmail.com>
> I noticed this on a fresh install from the usbinstamd64.bz2 downloaded
> today. I am typing the error. The error is while it is compiling the
> amd64 programs..
>
> [...]
> mk syscall
> sed '/#define...
> ....
> 6c -I/sys/src/libc/9syscall -FTVw syscall.c
> tab.h:52 syscall.c:34 name not declared: _nsec
> mk: 6c -I/sys ... : exit status=rc 20800: 6c 20802: error
> mk: for(i in 1a ... : exit status=rc 9085: rc 20789: mk 20792: error
> mk: test -e ... error
> mk: date for (i ... : ... error
> halt system? ...
ok. there must have been version skew. i rebuilt everything. but i'm traveling, so i didn't
do any sanity checking.
_nsec is just for binary compatability with the nsec system call. i'm still
unconvinced, but i don't want to introduce an incompatability like that either.
by the way, one of the least attractive things about an nsec system call is
high frequency high precision timing would be much better off with a
relative clock that is not adjusted. cf. the linux leap second fiasco.
TSC is probablly ideal for this on intel machines.
- erik
next prev parent reply other threads:[~2014-06-26 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 8:05 Ramakrishnan Muthukrishnan
2014-06-26 3:27 ` erik quanstrom [this message]
2014-06-26 7:21 ` Ramakrishnan Muthukrishnan
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=681eaf1b4ab51dffe048828421eb9801@ladd.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).