From: Keith M. <kei...@us...> - 2013-03-09 19:17:46
|
On 09/03/13 14:23, Earnie Boyd wrote: > On Fri, Mar 8, 2013 at 5:16 PM, Keith Marshall wrote: >> On 08/03/13 18:48, Earnie Boyd wrote: >>> On Fri, Mar 8, 2013 at 9:26 AM, Keith Marshall wrote: >>>> $(INC), or the alternative $(INCLUDES), maybe should, >>>> (but without the -I flag). >>> >>> Regardless of the -l flag the : is causing a multi-target to be defined. >> >> Well, both Eli and I would beg to disagree with this assertion; this, I >> think, must conclusively refute it: > > Okay, I misinterpreted the error message. Jim has violated the static > pattern rules. Sorry, but I just don't see how this is relevant. We have a saying in Britain: when you're in a hole, stop digging. Jim's usage doesn't even remotely resemble a static pattern rule. The actual issue is that he has tried to introduce an INCLUDES path spec as a dependency, which it isn't. It belongs within the commands section of the rule, where it would be logically introduced via CPPFLAGS; it has no place as a pre-requisite of the target. Eli has already correctly diagnosed the issue, and stated the solution; there's really no need to confuse matters, by continuing to pursue any more blind alleys. -- Regards, Keith. |