In data mercoledì 2008-09-17 14:26:33 +, Dave Korn ha scritto:
>
> Follow-up Comment #5, bug #18617 (project make):
>
> I would like to draw the attention of everyone in this thread to
>
> http://bashdb.sourceforge.net/remake/
> "Remake - GNU Make with comprehensible tracing and a debugger"
Follow-up Comment #5, bug #18617 (project make):
I would like to draw the attention of everyone in this thread to
http://bashdb.sourceforge.net/remake/
"Remake - GNU Make with comprehensible tracing and a debugger"
I find it an invaluable enhancement to make when debugging complex makefiles
ful
Follow-up Comment #4, bug #18617 (project make):
I was looking for the same feature, especially I'd like to trace the
invokation of implicit rules, it would be really usueful to see the implicit
rule invoked and the file where it is defined.
As an use case I'm currently debugging this (make -d):
Update of bug #18617 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Operating System:
Follow-up Comment #2, bug #18617 (project make):
You may try looking at
http://lists.gnu.org/archive/html/help-make/2006-10/msg00033.html.
Using the -P (preprocessing) feature shows partial expansions of $(eval)
invocations.
___
Reply to t
Follow-up Comment #1, bug #18617 (project make):
I would like to piggyback on this enhancement request. I would like to see
some manner of printing out the fully resolved makefile that make processes
after evaluating $(foreach), $(eval), and ($call) functions. For example,
consider this complicat
URL:
<http://savannah.gnu.org/bugs/?18617>
Summary: Better debugging facilities: tracing rule
invocation.
Project: make
Submitted by: None
Submitted on: Thursday 12/28/06 at 14:46 UTC
Severity: 3 -
On Wed, 17 Jan 2001 10:03:36 -0600, "James L. Peterson"
<[EMAIL PROTECTED]> wrote:
>A major problem that I have with make is being able to debug the
>makefiles. I end up working on big projects that are supposed to
>be for multiple platforms, so there are a lot of make variables
>and thousands o
%% Regarding Better Debugging; you wrote:
jlp> The -d debug flag gives some information, but not a lot. What
jlp> I would like to be able to see is:
Some would say it gives too much :)
jlp> (a) the values of all the variables
jlp> (b) what files are being included
jlp&g
A major problem that I have with make is being able to debug the
makefiles. I end up working on big projects that are supposed to
be for multiple platforms, so there are a lot of make variables
and thousands of lines of multiple makefiles. My difficulty is
in seeing what everything expands to, s
10 matches
Mail list logo
