Am Donnerstag, 5. Juni 2003, 04:35:47 Uhr MET, schrieb Olivier Thauvin:
> I am not sure if these behaviour will style happend but... I have this on
> sparc arch, and it seems other arch can be affect:
> line: 127
> # Must we lock files when doing compilation ?
> need_locks="yes"
Hmm, the libtool on i586 has need_locks set to no.
> line 801:
> if test "$need_locks" = yes; then
> until $run ln "$0" "$lockfile" 2>/dev/null; do
> $show "Waiting for $lockfile to be removed"
> sleep 2
> done
This is exactly the same code as in libtool 1.5.
> If you look, it make hard link, which of course failed if you build
> on another than libtool itself, this is case with my nfs /home and
> /usr. It start a loop which never end, because it wait to remove
> itself a file it can't create... replace ln by $LN_S should fix.
I don't understand this, do you mean it will fail if the linked file
is in a different partition?
--
What difference does it make to the dead, the orphans and the
homeless, whether the mad destruction is wrought under the name of
totalitarianism or the holy name of liberty or democracy?
Mahatma Gandhi (1869 - 1948), "Non-Violence in Peace and War"
