* Re[2]: [9fans] hehe bad to worse
@ 2001-05-10 16:27 presotto
2001-05-10 16:57 ` Re[3]: " Matt H
2001-05-10 17:47 ` Re[2]: " Axel Belinfante
0 siblings, 2 replies; 6+ messages in thread
From: presotto @ 2001-05-10 16:27 UTC (permalink / raw)
To: 9fans
my fault, I should have put a new port/portmkfile in the last wrap.
Just remove the
segment.$O: segment.h
line from portmkfile, segment.h is history, its contents are in segment.c.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re[3]: [9fans] hehe bad to worse
2001-05-10 16:27 Re[2]: [9fans] hehe bad to worse presotto
@ 2001-05-10 16:57 ` Matt H
2001-05-10 17:47 ` Re[2]: " Axel Belinfante
1 sibling, 0 replies; 6+ messages in thread
From: Matt H @ 2001-05-10 16:57 UTC (permalink / raw)
To: presotto@plan9.bell-labs.com
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re[2]: [9fans] hehe bad to worse
2001-05-10 16:27 Re[2]: [9fans] hehe bad to worse presotto
2001-05-10 16:57 ` Re[3]: " Matt H
@ 2001-05-10 17:47 ` Axel Belinfante
1 sibling, 0 replies; 6+ messages in thread
From: Axel Belinfante @ 2001-05-10 17:47 UTC (permalink / raw)
To: 9fans
Now I'm slightly confused. My /sys/src/9/port/portmkfile contains
segment.$O: ../port/segment.h
This is the line that is to be deleted, I assume, or???
For the record, AFAIK I succesfully applied both wraps, and succeeded
to remake everything, including kernels.
Axel.
> my fault, I should have put a new port/portmkfile in the last wrap.
> Just remove the
>
> segment.$O: segment.h
>
> line from portmkfile, segment.h is history, its contents are in segment.c.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re[3]: [9fans] hehe bad to worse
@ 2001-05-10 17:37 forsyth
0 siblings, 0 replies; 6+ messages in thread
From: forsyth @ 2001-05-10 17:37 UTC (permalink / raw)
To: 9fans
>>in /sys/src/9/pc/mkfile, ensure you've got:
>> pgrp.$O\
>> portclock.$O\
>> print.$O\
although true, ignore that: i misread the diagnostic as undefined not redefinition.
presotto's comment is correct.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re[3]: [9fans] hehe bad to worse
@ 2001-05-10 17:28 presotto
0 siblings, 0 replies; 6+ messages in thread
From: presotto @ 2001-05-10 17:28 UTC (permalink / raw)
To: 9fans
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re[3]: [9fans] hehe bad to worse
@ 2001-05-10 17:28 forsyth
0 siblings, 0 replies; 6+ messages in thread
From: forsyth @ 2001-05-10 17:28 UTC (permalink / raw)
To: 9fans
[-- Attachment #1: Type: text/plain, Size: 114 bytes --]
in /sys/src/9/pc/mkfile, ensure you've got:
pgrp.$O\
portclock.$O\
print.$O\
portclock.$O is new(ish)
[-- Attachment #2: Type: message/rfc822, Size: 2573 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2001-05-10 17:47 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-10 16:27 Re[2]: [9fans] hehe bad to worse presotto
2001-05-10 16:57 ` Re[3]: " Matt H
2001-05-10 17:47 ` Re[2]: " Axel Belinfante
2001-05-10 17:28 Re[3]: " forsyth
2001-05-10 17:28 presotto
2001-05-10 17:37 forsyth
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).