From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: Re[3]: [9fans] hehe bad to worse
Date: Thu, 10 May 2001 13:28:46 -0400 [thread overview]
Message-ID: <20010510172847.D4C9A19A0F@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
It looks like you somehow managed to not completely install
one of the wraps. I have a machine that we built with the
0327 full update and then has the 0425 and 0507 wraps applied
and it compiles kernels without a problem.
The addclock0link code moved from clock.c to port/portclock.c in the
0327 wrap to avoid doing the same thing in every architecture. The
0425 wrap reinstalls port/portclock.c to fix a bug. Looks lke you
still have a clock.c from before the 0327 version and also the
port/portclock.c
[-- Attachment #2: Type: message/rfc822, Size: 2378 bytes --]
From: Matt H <matt@proweb.co.uk>
To: "presotto@plan9.bell-labs.com" <9fans@cse.psu.edu>
Subject: Re[3]: [9fans] hehe bad to worse
Date: Thu, 10 May 2001 17:57:45 +0100
Message-ID: <872672673.20010510175745@proweb.co.uk>
Thursday, May 10, 2001, 5:27:32 PM, you wrote:
ppblc> my fault, I should have put a new port/portmkfile in the last wrap.
ppblc> Just remove the
ppblc> segment.$O: segment.h
ppblc> line from portmkfile, segment.h is history, its contents are in segment.c.
well that just gets me :
size 9pccpudisk
addclock0link: redefinition: addclock0link
(2517) TEXT addclock0link+0(SB),$16
mk: 8c -FVw '-DKERNDATE='`{date ... : exit status=rc 24694:8l 24698:error
cpu%
so something else has gone wrong. Maybe you did update it and my
wrap/inst didn't overwrite it
--
Best regards,
Matt mailto:matt@proweb.co.uk
next reply other threads:[~2001-05-10 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 17:28 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-10 17:37 forsyth
2001-05-10 17:28 forsyth
2001-05-10 16:27 Re[2]: " presotto
2001-05-10 16:57 ` Re[3]: " Matt H
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=20010510172847.D4C9A19A0F@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--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).