Re: Windows make invoking cygwin sh bug
Alex Khripin <[email protected]>
| Newsgroups | gmane.comp.gnu.make.windows |
|---|---|
| Message-ID | <[email protected]> |
Oh! I was using the one shipped with Cygwin. That apparently has HAVE_DOS_PATHS disabled. I've rebuilt it, and it's on its way to working! Thanks a lot. On Fri, Mar 18, 2011 at 2:28 PM, Eli Zaretskii <[email protected]> wrote: >> Date: Fri, 18 Mar 2011 14:10:15 -0400 >> From: Alex Khripin <[email protected]> >> Cc: [email protected] >> >> > Why are you using a native build of Make with Cygwin tools? Doing >> > that is asking for trouble due to subtle incompatibilities like this >> > one. The Cygwin build of Make is a much better candidate for this >> > kind of job, and it does support DOS/Windows file names with drive >> > letters. Can you use that instead? If not, why not? >> > >> > I tried this today with a simple Makefile that I ran with Cygwin's make: >> DIR=c:/temp >> >> $(DIR)/myfile2 : $(DIR)/myfile >> cp $^ $@ >> >> $(DIR)/myfile : >> @echo foo > $@ >> >> >> This does not work: >> Makefile:3: *** target pattern contains no `%'. Stop. >> >> Are you sure the cygwin make is meant to deal with Windows paths? > > I'm sure it did at some point, and that it still should. But that > assumes that what you have is a normal compilation of stock Make > sources, not sources that someone tweaked. > > Is the Make you have your own build? If not, can you build a Cygwin > port of Make yourself, making sure that HAVE_DOS_PATHS is defined to a > non-zero value in config.h. Then you will have a Cygwin build that > groks Windows file names with drive letters. If that build fails as > well, please report that as a bug. >