On Mon, 2011-04-04 at 01:07 -0400, Christopher Faylor wrote: > On Sun, Apr 03, 2011 at 07:22:42PM -0500, Yaakov (Cygwin/X) wrote: > >Without it, after a successfully completed build: > > > >$ make clean -C i686-pc-cygwin/winsup/cygwin > >[...] > >$ make > >[...goes until winsup/cygwin...] > >[...compiles all files until link stage...] > >g++: devices.o: No such file or directory > >make[3]: *** [cygwin0.dll] Error 1 > > > >So in this case, apparently it is. > > And, without it, I continue to build without problem. I *am* building > on Linux, though, so maybe that's the difference.
No, I duplicated this on Linux as well (after I tracked down a cocom RPM), but that did make me think of other possibilities. The difference seems to be if you pass an absolute or relative path to the top-level configure script; only in the latter does it fail as I described. I presume you've been using an absolute path? Yaakov
