This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cp and "are the same file"

On Sat, 18 Dec 2004, Max Bowsher wrote:

> 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
> > unknown Cygwin
> >
> > /etc/setup/installed.db says I have fileutils-4.1-2.tar.bz2
> >
> > cp --version says I have:
> > cp (fileutils) 4.1
> >
> > 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.

IIRC, method 1 (patched directory) packaging was supposed to contain a
reverse patch in the CYGWIN-PATCHES subdirectory...  I can't check at the
moment whether the fileutils package actually does.

> > 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
> > same file
> >
> > "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.

That said, I believe the OP didn't request that gcc not produce .exe files
by default, only how can *he* make gcc not produce the .exe suffix.  What
you have to do is add a "." after the output (-o) filename[*].  Some
projects define EXEEXT (or EXESUFFIX), so setting that to "." in yours
could be all you need.
[*] IOW, this works: 'gcc prog.c -o prog.' produces 'prog', not 'prog.exe'.
      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]