Re: win32 compilation of make 4.0 source code

[Philip Guenther]

(Dang it: gmail treats control-enter as "send"...)

On Mon, Jan 27, 2014 at 1:12 PM, Philip Guenther <address@hidden> wrote:
> On Mon, Jan 27, 2014 at 9:59 AM, Mark Brown <address@hidden> 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 .

This is where Paul question of "what did you already try?" comes in.
Rather than give you a fish, it would be better to teach you how to
fish; seeing what you tried would let us correct whatever
misunderstanding caused the syntax errors you got.

Or you could search the archives for examples, if you really don't
want to understand.


>> 2)  Also, please answer the other question posed:

Hmm, how much are you paying for these answers?  Oh right, nothing...


>> ---------------------------------------------------------------------------------------------------
>>
>> 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.
>> ---------------------------------------------------------------------------------------------------

Since you don't say what debug output you've already looked at, I'll
just suggest two possibilities
1) "make -pq" and examine the dumped output, which gives file and line
number for all commands
2) check out the "remake" project. http://bashdb.sourceforge.net/remake/


>> If either of these make capabilities are not possible currently,
>> then that is a case for implementation in  Make  version 4.1 .

You didn't describe the problem that you're trying to solve; how do
you know that data would solve it?  Why *only* automatic variables?
If there are several levels of variable expansion involved, what
should the output look like?


Philip Guenther