[bug #18872] problem colon after drive letter in prerequisite
Follow-up Comment #3, bug #18872 (project make): I'm fairly confident that cygwin's GCC will only generate dos-style paths in the output dependency files if you pass it in dos-style paths on the commandline or in #include statements. If it were to do so for any other reason, that would indeed be a bug, and I'd be very glad to see a testcase posted to the cygwin mailing list. cheers, DaveK ___ Reply to this item at: http://savannah.gnu.org/bugs/?18872 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #18872] problem colon after drive letter in prerequisite
Update of bug #18872 (project make): Status:None = Fixed Open/Closed:Open = Closed Component Version:None = 3.81 Fixed Release:None = CVS ___ Follow-up Comment #2: Only project admins can change the state of a bug (so you can't re-open it). If GCC is generated drive-lettered pathnames in a cygwin environment that is arguably a bug in GCC on Cygwin; you should report it to either or both GCC or Cygwin. However, as Eli points out there has already been a change incorporated to allow GNU make on Cygwin to handle drive letters properly (for some definition of properly). This change will be available in the next release of GNU make. ___ Reply to this item at: http://savannah.gnu.org/bugs/?18872 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #18872] problem colon after drive letter in prerequisite
URL: http://savannah.gnu.org/bugs/?18872 Summary: problem colon after drive letter in prerequisite Project: make Submitted by: mmilleder Submitted on: Wednesday 01/24/2007 at 15:56 Severity: 3 - Normal Item Group: None Status: None Privacy: Public Assigned to: None Open/Closed: Open Discussion Lock: Any Component Version: None Operating System: None Fixed Release: None ___ Details: Reopening bug 17105 (didn't find a way to do that, and didn't find any other bug for this problem) Example makefile: --- begin - all: c:/myfile.txt echo yes --- end --- Expected output --- begin - make: *** No rule to make target `c:/myfile.txt', needed by `all'. Stop. --- end --- Actual output: --- begin - Makefile:1: *** target pattern contains no `%'. Stop. --- end --- Environment (Windows XP SP2): --- begin - $ uname -a CYGWIN_NT-5.1 hostname 1.5.23(0.156/4/2) 2006-12-19 10:52 i686 Cygwin --- end --- Version, freshly built from the make-3.81 source archive: --- begin - $ make -v GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i686-pc-cygwin --- end --- Cygwin seem to have a patched version, linked from http://cygwin.com/ml/cygwin/2006-09/msg00153.html GCC on Cygwin produces such dependency entries with its -MF option. ___ Reply to this item at: http://savannah.gnu.org/bugs/?18872 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
[bug #18872] problem colon after drive letter in prerequisite
Follow-up Comment #1, bug #18872 (project make): You are using the Cygwin build of Make 3.81, which does not support drive letters in file names (I believe the announcement on the Cygwin mailing list at the time they released Make 3.81 explains why they discontinued support for drive letters.) I suggest to try the patched version of Cygwin Make 3.81, from the URL you cited: http://cygwin.com/ml/cygwin/2006-09/msg00153.html That version should support drive letters in file names. FWIW, the native (non-Cygwin) Windows build of Make 3.81 behaves as you expect: make: *** No rule to make target `c:/myfile.txt', needed by `all'. Stop. The above-mentioned patched Cygwin build uses the same code for drive letter support as the native build, so I have good reasons to believe your problems will be solved once you use the patched version. ___ Reply to this item at: http://savannah.gnu.org/bugs/?18872 ___ Message sent via/by Savannah http://savannah.gnu.org/ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
