* pws-19 + all patches: ``cp -f'' not always supportes
@ 1999-05-27 14:09 Andrej Borsenkow
1999-05-28 0:14 ` Timothy J Luoma
0 siblings, 1 reply; 3+ messages in thread
From: Andrej Borsenkow @ 1999-05-27 14:09 UTC (permalink / raw)
To: ZSH workers mailing list
Compiling it on the one of my old systems, I found, that configure bails out
trying to copy config.status -> config.status.old
Our cp does not support -f.
Is it possible to do without it? At least 3.1.5 compiled nicely on the same
system.
/andrej
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pws-19 + all patches: ``cp -f'' not always supportes
1999-05-27 14:09 pws-19 + all patches: ``cp -f'' not always supportes Andrej Borsenkow
@ 1999-05-28 0:14 ` Timothy J Luoma
1999-05-29 10:06 ` PATCH: " Bart Schaefer
0 siblings, 1 reply; 3+ messages in thread
From: Timothy J Luoma @ 1999-05-28 0:14 UTC (permalink / raw)
To: ZSH workers mailing list
Replying to message of Thu, 27 May 1999 18:09:20 +0400
from "Andrej Borsenkow" <borsenkow.msk@sni.de>
regarding ``pws-19 + all patches: ``cp -f'' not always supportes''
> Our cp does not support -f.
Neither does ours. (NeXTstep/OpenStep)
why not just use 'rm -f' before the 'cp' since that would be supported anywhere?
I'm not actually clear on when the '-f' flag would be needed....
TjL
^ permalink raw reply [flat|nested] 3+ messages in thread
* PATCH: Re: pws-19 + all patches: ``cp -f'' not always supportes
1999-05-28 0:14 ` Timothy J Luoma
@ 1999-05-29 10:06 ` Bart Schaefer
0 siblings, 0 replies; 3+ messages in thread
From: Bart Schaefer @ 1999-05-29 10:06 UTC (permalink / raw)
To: ZSH workers mailing list
On May 27, 6:09pm, Andrej Borsenkow wrote:
} Subject: pws-19 + all patches: ``cp -f'' not always supportes
}
} Our cp does not support -f.
}
} Is it possible to do without it?
On May 27, 8:14pm, Timothy J Luoma wrote:
} Subject: Re: pws-19 + all patches: ``cp -f'' not always supportes
}
} why not just use 'rm -f' before the 'cp'
Indeed, why not.
} I'm not actually clear on when the '-f' flag would be needed....
The file is a symlink? Somebody else owns it, but the build directory is
writable by you?
I'm not sure why it needs to be "cp" though. Why not "mv -f" instead?
However, this patch just does the "rm -f" thing.
Index: configure.in
===================================================================
--- configure.in 1999/05/29 10:02:04 1.20
+++ configure.in 1999/05/29 10:02:17
@@ -1298,7 +1298,8 @@
dnl The standard config.status is missing some essential features.
dnl So add them now.
-[cp -f $CONFIG_STATUS $CONFIG_STATUS.old
+[rm -f $CONFIG_STATUS.old
+ cp $CONFIG_STATUS $CONFIG_STATUS.old
sed '1,$s@^\( *ac_file_inputs=\).*$@\1`echo $ac_file_in | sed -e "s%^%:%" -e "s%:\\([^!]\\)% $ac_given_srcdir/\\1%g" -e "s%:!% %"`@' \
$CONFIG_STATUS.old >$CONFIG_STATUS
rm -f $CONFIG_STATUS.old]
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1999-05-29 10:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-05-27 14:09 pws-19 + all patches: ``cp -f'' not always supportes Andrej Borsenkow
1999-05-28 0:14 ` Timothy J Luoma
1999-05-29 10:06 ` PATCH: " Bart Schaefer
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).