This is the mail archive of the
mailing list for the Cygwin project.
Re: cp and "are the same file"
Jeremy C. Reed wrote:
I read messages about this from others in various list archives.
I am using cygwin. uname -a tells me:
CYGWIN_NT-5.1 myhost 1.5.12(0.116/4/2) 2004-11-10 08:34 i686 unknown
/etc/setup/installed.db says I have fileutils-4.1-2.tar.bz2
cp --version says I have:
cp (fileutils) 4.1
http://www.cygwin.com/packages/fileutils/ seems to indicate I have the
newest version. Is there a patch against the official fileutils (before
coreutils) or do I need to do it myself to see the changes?
Unfortunately, yes, you have to diff against the original in this case.
Most Cygwin packages have migrated to a
buildscriptscript+patch+original_tarball format, but not this one.
Anyways, I want to cp to magically see the .exe and copy correctly....
Example of error:
cp: `/home/jreed/tmp/bmake/bmake' and `/home/jreed/pkg/bin/bmake' are the
"are the same file" is the wrong message.
I am hoping to just improve cp to do the right thing versus fixing
numerous places that use it.
That would make sense.
I believe there is some (slow) on-going work to change to coreutils - ask on
this mailing list before you spend time patching the old fileutils.
Or maybe I can get gcc to stop saving with ".exe" suffix. It appears I
don't need ".exe" for my executables to work. Any ideas on how to get gcc
to not automatically append an ".exe".
The suffix is required on Win9x, AFAIK, so this is not a viable route.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html