Hi Marcin, * [EMAIL PROTECTED] wrote on Thu, Mar 31, 2005 at 09:41:57AM CEST: > Hello! > Libtool uses hard links for locking. It links itself to > the lockfile located in the libtooled project directory. > It doesn't work if the project and the libtool are on > different disk volumes. So the libtool hangs up. > I attach a patch which is just simple workaround of the > problem, but I'm sure you'll find sobe better solution. > (it is to be applied on ltmain.* files)
Your patch is not ok, as I already replied to you on savannah. Please answer the questions I posted there. > May anyone delete my post from patch manager on savannah? > (I didn't know that it would publish my email) I really don't know if setting the patch status to private will solve this.. .. but we'll find that out now. Whoever wants to follow this: see the archives for the libtool-patches list[1]. Regards, Ralf [1] http://lists.gnu.org/archive/html/libtool-patches/ > --- ltmain.in Sat Feb 12 13:18:34 2005 > +++ ltmain.in.new Thu Mar 31 09:29:41 2005 > @@ -807,9 +807,9 @@ > fi > > # Lock this critical section if it is needed > - # We use this script file to make the link, it avoids creating a new file > + # We use this script file to make the link > if test "$need_locks" = yes; then > - until $run ln "$progpath" "$lockfile" 2>/dev/null; do > + until $run $LN_S "$progpath" "$lockfile" 2>/dev/null; do > $show "Waiting for $lockfile to be removed" > sleep 2 > done
