Re: Re[3]: [9fans] hehe bad to worse

Re: Re[3]: [9fans] hehe bad to worse

[forsyth]

>>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.

Re: Re[3]: [9fans] hehe bad to worse

[presotto]

[-- 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

Re: Re[3]: [9fans] hehe bad to worse

[forsyth]

[-- 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

Re[3]: [9fans] hehe bad to worse

[Matt H]

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