On Mon, Jan 27, 2014 at 9:59 AM, Mark Brown <mkbrown_...@hotmail.com> wrote: > First, let me request that you include the question posed to you, > in your Reply responses in this email sequence.
How about you stop top-posting and instead reply inline? > 1) I think my question was explicit. > A method for an existing Makefile to test for .FEATURES capabilities > when it is downloaded to a random linux or Windows make environment > and existed. <sigh> That wasn't the question you originally asked. To quote your original query about .FEATURES: >> As a separate related issue, >> I was try to echo the .FEATURES information, since one of the its it claims >> to display >> mentions its Else If capabilities. >> However, every time I tried to echo the data I received a syntax error. >> What would be an example of a Makefile contents which would display >> the .FEATURES information ? The example that Paul gave answers that original question: all: echo ${.FEATURES} So now you have a new question > The Makefile itself when e.g "make <target>" is selected, should be > able to precede execution of any target with a check of .FEATURES > to verify the make environment into which it is downloaded. > Give an example of .FEATURES display/echo in an existing Makefile., > both v 3.80 and 4.00 . > > 2) Also, please answer the other question posed: > --------------------------------------------------------------------------------------------------- > > I also want to know if there is a debug mode within make > in which the Makefile filename and Line Number > (some Makefiles are huge and distributed over several subordinate Makefiles) > is matched to each automatic variable evaluation within a Target evaluation. > --------------------------------------------------------------------------------------------------- > > If either of these make capabilities are not possible currently, > then that is a case for implementation in Make version 4.1 . > > > > > -----Original Message----- From: Paul Smith > Sent: Monday, January 27, 2014 9:35 AM > To: Mark Brown > Cc: bug-make@gnu.org > > Subject: Re: win32 compilation of make 4.0 source code > > On Sun, 2014-01-26 at 16:22 -0800, Mark Brown wrote: >> >> That example method is a device to perform this .FEATURES test >> without inserting it into an existing Makefile. >> The syntax errors I was seeing were occurring when attempting to insert >> this >> test into an existing Makefile, full of Targets and command sequences. > > > Well, since you've provided no details about exactly what you tried and > what errors you received, or even details about exactly what you're > trying to do, there's not much else we can say. You said "echo the > data", and I showed an example of echoing the data. If that's not what > you want, you need to give more information. > > ============================================================ > ==========re-pasted text of the question posed===================== > ============================================================ > > That example method is a device to perform this .FEATURES test > without inserting it into an existing Makefile. > The syntax errors I was seeing were occurring when attempting to insert this > test > into an existing Makefile, full of Targets and command sequences. > If this feature is used it would be at the top of an existing Makefile, > before any targets > are evaluated. > > I also want to know if there is a debug mode within make > in which the Makefile filename and Line Number > (some Makefiles are huge and distributed over several subordinate Makefiles) > is matched to each automatic variable evaluation within a Target evaluation. > ============================================================= > > > > _______________________________________________ > Bug-make mailing list > Bug-make@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-make _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make