In <[EMAIL PROTECTED]>, Marcel Moolenaar wrote:
> Martin Cracauer wrote:
> >
> > In <[EMAIL PROTECTED]>, Marcel Moolenaar wrote:
> > > It seems to me that when there's a PATH= assignment you don't want to
> > > add anything to the cache or alternatively, clear the cache after
> > > execution of the command having a PATH= assignment.
> >
> > The first solution is better, but the source messes with the hashtable
> > too directly in too many places.
> >
> > Appended diff does the second route. Does it fix your problems?
>
> It fixes the examples and thus my problems :-)
>
> I already created a work-around in `make buildworld' so it works on
> older shells without the need to build sh(1) in the bootstrap stage,
> because the bug only pops up when doing a parallel make (ie make -jN)
> because each command will be executed by the same shell instance in that
> case.
I would like you to do so, since I'd like to give the better solution
a shot over the weekend.
> BTW: Don't forget to remove '-g' from CFLAGS when you commit the patch
> :-)
Ops :-) Now working with a seperate Makefile (for bumping Warning
levels).
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/
Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
