newvers.sh: can't find dirname?

[Garrett Cooper]

On Wed, Nov 17, 2010 at 12:23 PM, Warner Losh <imp at bsdimp.com> wrote:
> On 11/17/2010 12:36, Garrett Cooper wrote:
>>
>>    This is the second time I've seen this (I forgot why I fixed it the
>> first time, reverted the local change, and ran into the change the
>> second time):
>>
>> ===>  include (install)
>> creating osreldate.h from newvers.sh
>> NEWVERS PATH:
>> /usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.Nuxzcgf9
>> /usr/src/include/../sys/conf/newvers.sh: dirname: not found
>
> This shouldn't be running newvers.sh...

This might be because sys/param.h was newer than osreldate.h (I
unpacked it from a tarball as it was on a memory disk). I thought tar
was supposed to preserve the file dates and times with -p though -_-:

     -m, --modification-time
             (x mode only) Do not extract modification time.  By default, the
             modification time is set to the time stored in the archive.

>> # dirname
>> usage: dirname string [...]
>>
>>    I hacked around this by adding dirname to $PATH in newvers.sh (if
>> you look at the above $PATH printed out, it doesn't contain /bin and
>> /usr/bin -- both which are required to run the above commands), but I
>> was wondering if anyone else has run into this issue before, and
>> whether or not a better solution was in the works (maybe).

Thanks,
-Garrett