This is the mail archive of the cygwin@sourceware.cygnus.com 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] |
Hello!
My name is Konstantin Terletskiy. I
used CYGWIN Beta 19.1 a lot to port various UNIX utilities on NT. In most cases
everything is OK, but most of the products have 'make install' step to install
product to correct directories. Once tool has been built, it definitely has new
<exec.exe> files to be installed. But makefile usually fails to do it
reporting <exec>: No such file or directory. That's because makefile was
written for pure UNIX, where executive file lloks like <exec>. But
actually <exec.exe> exists. Even if I type 'ls <exec>' it shows that
'<exec>' exist and actually <exec> points to <exec.exe>. But
if I try 'cp <exec> <exec>.1' it reports 'No such file or
directory'. Ok, I could correct Makefile to deal explicitly with
<exec.exe> and, after that, it works fine. But some distributions (as, for
example, X11R6.3) rely on that issue too much, so a lot of changes should be
done to make it buildable. And what is really confusing is that for 'ls' command
<exec> exists as well as <exec.exe>, BUT for cp and mv commands only
<exec.exe> exists, BUT not <exec>! I cannot also say 'ln -s exec.exe
exec', because for ln <exec> already exists.
May be somebody knows how to fight with this
problem?
Konstantin Terletskiy
|
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |