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
Le Jeudi 05 Juin 2003 15:35, Götz Waschk a écrit :
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
Am Donnerstag, 5. Juni 2003, 16:22:26 Uhr MET, schrieb Olivier Thauvin:
I don't understand this, do you mean it will fail if the linked file
is in a different partition?
ln is not ln -s, $LN_S is ln -s, of course ln failed over mount
point ! Just try ;)
I know this, hard links have to be
Le Jeudi 05 Juin 2003 16:26, Götz Waschk a écrit :
Am Donnerstag, 5. Juni 2003, 16:22:26 Uhr MET, schrieb Olivier Thauvin:
I don't understand this, do you mean it will fail if the linked file
is in a different partition?
ln is not ln -s, $LN_S is ln -s, of course ln failed over mount
Am Donnerstag, 5. Juni 2003, 17:19:32 Uhr MET, schrieb Olivier Thauvin:
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
run=
then it run:
ln /usr/bin/libtool foobar.o.lock
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
line 801:
if test $need_locks = yes; then
until $run ln $0 $lockfile 2/dev/null; do
$show
