Re: Automake's file locking

2021-02-03 Thread Nick Bowler
On 2021-02-03, Bob Friesenhahn wrote: > GNU make does have a way to declare that a target (or multiple > targets) is not safe for parallel use. This is done via a > '.NOTPARALLEL: target' type declaration. According to the manual[1], prerequisites on .NOTPARALLEL target are ignored and this will

Re: Automake's file locking

2021-02-03 Thread Bob Friesenhahn
On Wed, 3 Feb 2021, Zack Weinberg wrote: Therefore I like the idea of merely relying on the atomicity of file creation / file rename operations. These files should reside inside the autom4te.cache directory. I would not like to change all my scripts and Makefiles that do rm -rf autom4te.cache

Re: Automake's file locking

2021-02-03 Thread Zack Weinberg
On Thu, Jan 28, 2021 at 6:51 PM Bruno Haible wrote: > Zack Weinberg wrote: > > There is a potential way forward here. The *only* place in all of > > Autoconf and Automake where XFile::lock is used, is by autom4te, to > > take an exclusive lock on the entire contents of autom4te.cache. > > For thi

RE: PLV, PSV in manual

2021-02-03 Thread DUDZIAK Krzysztof
Good to know. Thanks for info. Those automake variables, where primaries and prefixes specifying installation destination are used. I see the source of knowledge I use is it where mentioned terms have been introduced/used. -Original Message- From: Zack Weinberg [mailto:za...@panix.com]