9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/src/9/port/devsd.c
Date: Fri,  2 Jan 2004 16:35:44 -0500	[thread overview]
Message-ID: <ca4ab918be6eb9e3fecacec407283072@plan9.bell-labs.com> (raw)
In-Reply-To: <20040102185042.B25949@cackle.proxima.alt.za>

[-- Attachment #1: Type: text/plain, Size: 52 bytes --]

They're in pc/dat.h on sources.  You're out of date.

[-- Attachment #2: Type: message/rfc822, Size: 3093 bytes --]

From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] /sys/src/9/port/devsd.c
Date: Fri, 2 Jan 2004 18:50:42 +0200
Message-ID: <20040102185042.B25949@cackle.proxima.alt.za>

Last changed 12 December, reports

	8c -FVw -I. ../port/devsd.c
	../port/devsd.c:1007 not a function
	../port/devsd.c:1007 syntax error, last name: Devport

when trying to

	mk 'CONF=pcdisk' 9pcdisk.gz

or

	mk 'CONF=pc' 9pc.gz

Hm, I also get

	8c -FVw -I. ../port/proc.c
	../port/proc.c:156 not a member of struct/union: readied
	../port/proc.c:157 not a member of struct/union: schedticks
	../port/proc.c:190 not a member of struct/union: schedticks
	../port/proc.c:191 not a member of struct/union: readied
	../port/proc.c:208 not a member of struct/union: readied
	../port/proc.c:411 not a member of struct/union: readied
	../port/proc.c:495 not a member of struct/union: readied

which makes me suspicious that I may have a dated ../port.

Replica/pull does not have a "check" mode that would report if any
file is out of date, has it?  Mind you, it's as fast just to reload
everything, isn't it?

++L

  parent reply	other threads:[~2004-01-02 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 16:50 Lucio De Re
2004-01-02 17:22 ` andrey mirtchovski
2004-01-02 17:42 ` Russ Cox
2004-01-02 21:35 ` David Presotto [this message]
2004-01-03  8:37   ` Lucio De Re

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=ca4ab918be6eb9e3fecacec407283072@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /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).