Greetings,

I apologize for beating the heck out of the group.  I admit that some of my
questions are premature.  I appreciate everyones help.

I have a better handle on what is going on, and with that knowledge, I was
able to restructure the mkfile to work correctly in parallel.  I am
encountering a new problem, however.

Mk (and make) look at file times to determine what needs to be built.
 Cool.  When I type "mk" my app builds just fine.  The problem is that if I
type "mk" again, it (at least) partially builds again.  If I keep doing
this, eventually it says my target is up-to-date.

What I think is going on is that this little test app builds so fast that
the file write times look like they are the same time.  For example if I
build main.c and then do:

    ls -lrt

I should see them listed in this order:

    main.c
    main.8
    main

but sometimes I see them like this:


    main.c
    main
    main.8

I think this is caused because the time slice is too short and the system
can't tell the build times apart.  Even though main clearly came after main.8
the system sees them as the same time.  Of course this can cause mk to
dothe link again unnecessarily if
mk is called again.  This is what is happening to me.  Each time I mk it
builds less.

Perhaps this is a problem with 9port under VMware.  Perhaps, in certain
environments, the time slices are too big.

Any experience or thoughts on the matter are greatly appreciated.


Blake