Update of bug #25493 (project make):
Status:None => Duplicate
Open/Closed:Open => Closed
___
Follow-up Comment #1:
This is a duplicate o
URL:
<http://savannah.gnu.org/bugs/?25493>
Summary: -include filename does not show correct dependency
errors
Project: make
Submitted by: willard
Submitted on: Wed 04 Feb 2009 09:52:12 PM GMT
Severity: 3 -
On Wed, 2009-01-28 at 13:27 -0800, willard wrote:
>
> I am new to this message board... I did not intend to yell...
> Thanks for the info... I hope the Gnu Make developers are listening to
> bug-m...@gnu.org.
> I had a quick look at the CVS tree bug tracking (on sourceforge.net), and I
> didn't s
ssage in context:
http://www.nabble.com/-include-filename-does-not-show-correct-dependency-errors-tp21699973p21715450.html
Sent from the Gnu - Make - Bugs mailing list archive at Nabble.com.
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gn
On Wed, Jan 28, 2009 at 9:39 AM, willard wrote:
> it's the same if foo.d is not a direct target. It's even worse as make fails
> without ANY error message.
Nice! xxx.h gets marked as failed and the error silenced, and the
silencing applies to all paths to xxx.h and not just the foo.d->xxx.h
path
he 'make -f bad2.mak' shows no message at all..(but going thru a
makefile shows Error 2).
I am sure I can find a work-around, but this seems like a nasty bug THAT
SHOULD BE FIXED.
--
View this message in context:
http://www.nabble.com/-include-filename-does-not-show-correct-dependency-
On Tue, Jan 27, 2009 at 9:44 PM, willard wrote:
> this is my example (create the foo.d manually as below)
Well, now that you've shown your whole Makefile, I have a guess as to
why make is behaving as it is. It's tied that the face that you use
foo.d both as an implicit target (by virtue of being
on the include...
See that the good.mak really displays what the problem is... whereas the
bad.mak messages are not helpful.
--
View this message in context:
http://www.nabble.com/-include-filename-does-not-show-correct-dependency-errors-tp21699973p21700324.html
Sent
On Tue, Jan 27, 2009 at 8:59 PM, willard wrote:
> When using the "-include filename"(instead of just "include filename"), if
> this filename includes dependencies that are missing, makefile does not show
> those missing dependencies...
>
> For example, if using:
>
> -include foo.d
>
> with foo.d b
generate an error, but I would expect the content of foo.d
to be used normally
Looks like a bug to me.
Btw, I am using make 3.81.
--
View this message in context:
http://www.nabble.com/-include-filename-does-not-show-correct-dependency-errors-tp21699973p21699973.html
Sent from the Gn
10 matches
Mail list logo
