Re: [patch #3872] locking in libtool

[Marcin Siennicki]

> > > But the problem was on my machine (I moved to gcc-3.4, and I
> > > had rpm macros with deprecated options, so I get:
> > >      
>
> OK.  Easiest workaround would be to remove these options.  
I've fixed it already. I've found it after I saw that you were amazed 
why I had
locking enabled. So I started to look for the reason, and that caused 
the bug
report for rpm in Owl-linux :)

> Does apr-util use a preinstalled libtool (like /usr/bin/libtool) or does
> it build its own (like $top_builddir/libtool)?
>  
apr-util uses libtool installed with apr.

> Suggestions appreciated.
>  
Maybe the way could be creating unique lockfile in the destination directory
and then hardlinking to it?

Marcin