Date: Wed, 15 Dec 1999 13:16:21 +0100 From: Marcel Moolenaar <marcel@scc.nl> To: Martin Cracauer <cracauer@cons.org> Cc: current@FreeBSD.ORG Subject: Re: sh(1) broken caching [was: Re: Broken sh(1)?] Message-ID: <38578695.D41619A9@scc.nl> References: <712.945183175@axl.noc.iafrica.com> <38565DEA.4487DF53@scc.nl> <19991215105728.A61202@cons.org> <38576BD2.21701740@scc.nl> <19991215122546.A24027@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin Cracauer wrote: > > In <38576BD2.21701740@scc.nl>, 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. BTW: Don't forget to remove '-g' from CFLAGS when you commit the patch :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38578695.D41619A9>