[9fans] Fossil or something else altogether?

[9fans] Fossil or something else altogether?

[lucio]

I got the following while trying to build /386/lib/libsec.a:

ar 490: suicide: sys: trap: fault write addr=0x4 pc=0x00001077
mk: ar vu /386/lib/libsec.a ...  : exit status=rc 488: ar 490: sys: trap: fault write addr=0x4 pc=0x00001077

which I resorted to after failing to link a CPU kernel:

size 9fiddle
setupDESstate: /386/lib/libsec.a(setupDES3state): opcode out of range 0
	probably not a .8 file

... thinking that perhaps the library had been corrupted.

Now I'm quite baffled, this is not a problem I have encountered before.

++L

Re: [9fans] Fossil or something else altogether?

[David Presotto]

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

mk clean and remove the .a

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

From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] Fossil or something else altogether?
Date: Fri, 20 Jun 2003 17:42:56 +0200
Message-ID: <b43749f0b45b468f4551f0fcc16824a7@proxima.alt.za>

I got the following while trying to build /386/lib/libsec.a:

ar 490: suicide: sys: trap: fault write addr=0x4 pc=0x00001077
mk: ar vu /386/lib/libsec.a ...  : exit status=rc 488: ar 490: sys: trap: fault write addr=0x4 pc=0x00001077

which I resorted to after failing to link a CPU kernel:

size 9fiddle
setupDESstate: /386/lib/libsec.a(setupDES3state): opcode out of range 0
	probably not a .8 file

... thinking that perhaps the library had been corrupted.

Now I'm quite baffled, this is not a problem I have encountered before.

++L

Re: [9fans] Fossil or something else altogether?

[Lucio De Re]

On Fri, Jun 20, 2003 at 12:15:25PM -0400, David Presotto wrote:
> Lines: 58
>
> mk clean and remove the .a

No, it won't complete a rebuild of libsec.a.  Acid reveals:

acid: lstk()
main(argc=0x33,argv=0x7fffed14)+0x57 /sys/src/cmd/ar.c:171
	cp=0x0
_main+0x31 /sys/src/libc/386/main9.s:16
acid:

which is absurd (but probably true) because in the source that is the
exits("error") command as a result of an invalid command line option.

I think I have my filesystems mixed up too much (hence the subject)
with the nett result that the kernel is out of sync with the
executables.  I'll dig a little deeper...

++L