From: westki AT erols DOT com (Westki E-Mail Account) Subject: B19.1: make install scripts fail - trying to cp instead of 13 Nov 1998 11:39:48 -0800 Message-ID: <002b01be0e57$a39e5980$1a0101c0.cygnus.gnu-win32@simserver> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01BE0E2D.BA1A5E40" To: This is a multi-part message in MIME format. ------=_NextPart_000_0028_01BE0E2D.BA1A5E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 = files to be installed. But makefile usually fails to do it = reporting : No such file or directory. That's because makefile was = written for pure UNIX, where executive file lloks like . But = actually exists. Even if I type 'ls ' it shows that = '' exist and actually points to . But if I try = 'cp .1' it reports 'No such file or directory'. Ok, I could = correct Makefile to deal explicitly with 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 = exists as well as , BUT for cp and mv commands only = exists, BUT not ! I cannot also say 'ln -s exec.exe exec', because = for ln already exists. May be somebody knows how to fight with this problem? = Konstantin Terletskiy ------=_NextPart_000_0028_01BE0E2D.BA1A5E40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello!

My name is Konstantin = Terletskiy. I=20 used CYGWIN Beta 19.1 a lot to port various UNIX utilities on NT. In = most cases=20 everything is OK, but most of the products have 'make install' step to = install=20 product to correct directories. Once tool has been built, it definitely = has new=20 <exec.exe> files to be installed. But makefile usually fails to do = it=20 reporting <exec>: No such file or directory. That's because = makefile was=20 written for pure UNIX, where executive file lloks like <exec>. But = actually <exec.exe> exists. Even if I type 'ls <exec>' it = shows that=20 '<exec>' exist and actually <exec> points to = <exec.exe>. But=20 if I try 'cp <exec> <exec>.1' it reports 'No such file or=20 directory'. Ok, I could correct Makefile to deal explicitly with=20 <exec.exe> and, after that, it works fine. But some distributions = (as, for=20 example, X11R6.3) rely on that issue too much, so a lot of changes = should be=20 done to make it buildable. And what is really confusing is that for 'ls' = command=20 <exec> exists as well as <exec.exe>, BUT for cp and mv = commands only=20 <exec.exe> exists, BUT not <exec>! I cannot also say 'ln -s = exec.exe=20 exec', because for ln <exec> already exists.

May be somebody knows how to fight with = this=20 problem?

&nbs= p; = ; = &= nbsp; &n= bsp; &nb= sp; &nbs= p; = ;=20 Konstantin Terletskiy

------=_NextPart_000_0028_01BE0E2D.BA1A5E40-- - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".