From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3331b30fa3a10c850e81a49baaf22869@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mkfile question: mklib & co.
From: Charles Forsyth <forsyth@terzarima.net>
Date: Sat,  5 Aug 2006 21:27:50 +0100
In-Reply-To: <ee9e417a0608050842o19d45e6cg8118e8e16ba645e4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9780194a-ead1-11e9-9d60-3106f5b1d025

> also, /$objtype/include does not hold many header files
> at all.  the portable headers go in /sys/include, and only
> machine-dependent headers (u.h) go in /$objtype/include.

term% wc -l /386/include/*.h
     64 /386/include/u.h
     25 /386/include/ureg.h
     89 total

term% wc -l /power/include/*.h
     84 /power/include/u.h
     51 /power/include/ureg.h
    135 total

that one tiny fact makes an enormous difference.  try wading through
the tar pits of /usr/include on linux by comparison.
who could write so much of that stuff and apparently leave with the
satisfaction of a job well done?