make libc fails
Liam J. Foy
liamfoy at sepulcrum.org
Mon Sep 27 14:16:11 PDT 2004
On Mon, 27 Sep 2004 14:08:44 -0700 (PDT)
Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
>
> :
> :On Mon, 27 Sep 2004 13:05:15 -0700 (PDT)
> :Matthew Dillon <dillon at xxxxxxxxxxxxxxxxxxxx> wrote:
> :
> :> You need to do a buildworld/installworld sequence to get the updated
> :> include files before you can build subsystems singly.
> :
> :Hmm, I was sure I did do that. Starting it all again has solved my problem.
> :My bad! Thanks.
>
> Another thing that you (and everyone) should watch out for are stale
> files in /usr/src from manual builds (e.g. like the one you just tried
> to do in libc). These can cause odd problems later on. To clean those
> out type 'make cleandir; make clean' in /usr/src.
>
> When building a program or library manually you can keep /usr/src clean
> by doing a 'make obj' before 'make', which will cause the build to put
> generated files (like object files) in /usr/obj/usr/src/<blah> rather
> then /usr/src/<blah>.
>
> The 'make obj' trick is also used by people who have multiple machines,
> by allowing one machine to hold a master copy of /usr/src and then
> do a read-only NFS export of /usr/src to the other machine(s).
>
> [a buildworld creates its own object hierarchy in /usr/obj, you do not
> need to do anything special for buildworlds].
>
> -Matt
>
Note taken - thanks Matt. I will also be looking at rpc.rstatd soon. It is slowly
creeping up my Todo list. Once I have finished a few more things, I will then begin
to look at it.
--
-Liam J. Foy
http://liamfoy.kerneled.org
More information about the Bugs
mailing list