X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: make 3.81-1 vs. 3.80-1 and C:\... style dependency handling differences Date: Fri, 21 Jul 2006 16:17:28 -0700 Message-ID: From: To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k6LNHbWo005240 Hi. The following GNUmakefile behaves differently in the new 3.81-1 build compared to the 3.80-1 that was replaced. I did not find this subject when I looked at the recent messages. === default: C:\cygwin\bin/echo.exe "C:\cygwin\bin/echo" "Test" === 3.80-1 produces: $ make "C:\cygwin\bin/echo" "Test" Test === 3.81-1 produces: $ make GNUmakefile:1: *** target pattern contains no `%'. Stop. === Which is right for cygwin? I have a context that is now very dependent on 3.80-1's behavior. Is the context dependent on a mistake? Or is the new 3.81-1 not doing something it should? The actual GNUmakefile's use $(...) macros from environment variables that have Windows style paths. I vastly simplified the above to make the example. I simply replaced the make package with cygwin's setup.exe to go back and forth, with the rest of the environment unchanged and current according to setup.exe. Mark Millard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/