Mail Archives: cygwin/2001/05/28/07:25:40
OK. Having looked a little further into the mailing list archives, I see
that this problem is wrapped around executable (.EXE) files. According to
the threads, there was a patch to at least fix the error code. Doesn't look
to me like it made it into 1.3.2.
Anyway, sorry for the wasted bandwidth... though I must comment that it's
somewhat confusing to show via "ls" the filename with the ".EXE" stripped if
that's what it's inode really says it is....
-Mike
----- Original Message -----
From: "Michael Williamson" <mikewill AT twcny DOT rr DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, May 27, 2001 7:54 PM
Subject: Fw: Bug/Help on cp and mv using 1.3.2?
>
> ----- Original Message -----
> From: Michael Williamson
> To: cygwin AT cygwin DOT com
> Sent: Sunday, May 27, 2001 7:52 PM
> Subject: Bug/Help on cp and mv using 1.3.2?
>
>
>
> ----- Original Message -----
> From: Michael Williamson
> To: cygwin-subscribe AT cygwin DOT com
> Sent: Sunday, May 27, 2001 7:46 PM
> Subject: subscribe
>
>
> Not sure if this will get posted to the list, but:
>
> I am using 1.3.2 cygwin, and I was trying to build the meta object
compiler
> for qt, and I have run into a bizarre bug(??). Check out the data below:
>
> -Mike Williamson
> mikewill AT twcny DOT rr DOT com
>
>
> mike AT BOXYA123 ~
> $ cd /usr/local/qt
>
> mike AT BOXYA123 /usr/local/qt
> $ make
> make[1]: Entering directory `/usr/local/qt-2.3.0'
> cd src/moc; make
> make[2]: Entering directory `/usr/local/qt-2.3.0/src/moc'
> make[2]: Nothing to be done for `all'.
> [ comment from mike---- the build/link for moc worked fine prior to the
> next round of make commands ]
> make[2]: Leaving directory `/usr/local/qt-2.3.0/src/moc'
> rm -f bin/moc
> cp src/moc/moc bin/moc
> cp: `src/moc/moc' and `bin/moc' are the same file
> make[1]: *** [src-moc] Error 1
> make[1]: Leaving directory `/usr/local/qt-2.3.0'
> make: *** [init] Error 2
>
> mike AT BOXYA123 /usr/local/qt
> $ file src/moc/moc
> src/moc/moc: executable, can't read `src/moc/moc' (No such file or
> directory).
>
> mike AT BOXYA123 /usr/local/qt
> $ src/moc/moc
> this should create an error message
> standard input:0: Warning: No relevant classes found. No output generated.
>
> mike AT BOXYA123 /usr/local/qt
> $ ls -l src/moc/moc
> -rwxr-xr-x 1 mike 544 450262 May 27 17:42 src/moc/moc
>
> mike AT BOXYA123 /usr/local/qt
> $ cd src/moc
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ mv moc moc1
> mv: `moc' and `moc1' are the same file
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ ls moc1
> ls: moc1: No such file or directory
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ $ touch moc1
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ ls -l moc1
> -rw-r--r-- 1 mike 544 0 May 27 19:43 moc1
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ mv moc moc1
> mv: `moc' and `moc1' are the same file
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ diff moc moc1
> diff: moc: No such file or directory
>
> mike AT BOXYA123 /usr/local/qt/src/moc
> $ ls -l moc
> -rwxr-xr-x 1 mike 544 450262 May 27 17:42 moc
>
>
>
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -