Re: [patch #3872] locking in libtool

[Ralf Wildenhues]

Marcin,

* Marcin Siennicki wrote on Thu, Mar 31, 2005 at 02:31:11PM CEST:
> 
> >>>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.

OK, thanks.

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

Ugly, but possible.  Libtool would have to leave it around after
running: you may not remove it because then another instance may want to
link to it right afterwards.  Sounds like it should be below .libs/.
I still really don't like the idea that we may need to create .libs only
for this purpose (if all objects belong in subdirs, .libs need not
exist).   :-/

Regards,
Ralf