Message-Id: <200009190625.CAA19901@delorie.com> Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Felix Lee To: cygwin AT sourceware DOT cygnus DOT com Subject: weirdness in winsup/Makefile.common Date: Mon, 18 Sep 2000 23:24:37 -0700 So I spent an annoying amount of time in a wild goose chase because of this piece of code in Makefile.common: %.o: %.cc ifdef VERBOSE $(COMPILE_CXX) -o $(@D)/$(*F)$o $< else @echo $(CC) $c $(CXXFLAGS) ... $(*F).cc @$(COMPILE_CXX) -o $(@D)/$(*F)$o $< endif cygwin wasn't building on my machine for an odd reason, so I cut+paste the compile command that was in the make output, and it didn't work, because, among other things, '...' isn't a file name. it took me way too long to figure out where the '...' was coming from. but I'm wondering, why do this at all? it's not like the elision simplifies the output much (CXXFLAGS is several thousand chars long), and it introduces an extra step when you're trying to isolate a build problem. can this weirdness be deleted, please? -- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com