From mboxrd@z Thu Jan  1 00:00:00 1970
From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
References: <86ipu0evi2.fsf@cmarib.ramside>
	<95260b7e190c22af011c28169a4b2c38@brasstown.quanstro.net>
	<86oc3sv31d.fsf@cmarib.ramside>
	<1fda448af4d14fd45e11fc96eb572eef@ladd.quanstro.net>
	<864o5ipg2z.fsf_-_@cmarib.ramside>
	<139b00c13de072ed8b51dd8629ccf849@coraid.com>
Date: Thu, 28 Apr 2011 16:16:46 +0000
In-Reply-To: <139b00c13de072ed8b51dd8629ccf849@coraid.com> (erik quanstrom's
	message of "Thu, 28 Apr 2011 11:30:22 -0400")
Message-ID: <86d3k6nyfl.fsf@cmarib.ramside>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [9fans] Compiling 9atom kernel WAS: Re: spaces in filenames
Topicbox-Message-UUID: d77c5072-ead6-11e9-9d60-3106f5b1d025

erik quanstrom <quanstro@labs.coraid.com> writes:


>>     size 9pcf
>>     _strayintrx: _tracein/_traceout not defined 5 5
>>     _strayintrx: _tracein: not defined
>>     _strayintrx: _traceout: not defined
>>     mk: 8c -FTVw '-DKERNDATE='`{date ...  : exit status=rc 5800: 8l 5804: error
>
> _straintrx is a red herring.  have you recompiled libc?

Yes, I'm sure.  :) In typical paranoid newbie fashion, I made sure to do
an 'ls -l /386/lib' before trying to build the kernel... oh, wait.  Let
me try a 'mk clean' first... nope.  Same error.

Remember, I'm running your 9atom 9pcf.gz, with quanstro/fis, on an
otherwise stock P9 4e fossil+venti system.

Hm.  The /386/lib/libc.a and the one on /n/dump have the same exact
size.  But they have different contents (cmp differ @ char 26).  It sure
looks like I recompiled and installed libc.

--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com             PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+