[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: when gnu-make is missing a dependency
From: |
Randy Yates |
Subject: |
Re: when gnu-make is missing a dependency |
Date: |
09 May 2005 09:49:57 -0400 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence) |
"Paul D. Smith" <psmith@gnu.org> writes:
> %% Randy Yates <yates@ieee.org> writes:
>
> >> Possible reasons are (a) that file does exist, maybe on VPATH, or
> >> (b) you have a target "lpc.o" in your makefile with no rule or
> >> prerequisites (see the section "Rules without Commands or
> >> Prerequisites" in the GNU make manual).
>
> ry> Thanks for the timely response, Paul. If (a) were the case, then
> ry> why wouldn't I get a "Target is up-to-date" response instead of
> ry> "nothing to be done" when I "make lpc.o"?
>
> Yes, so it's probably the second one.
>
> "make -d" should tell you for sure though. And you can use "make -p" to
> see the rules database; search it for that target.
I got it now, Paul. I'm building under cygwin and that environment provides an
opportunity for some inconsistencies in path names, namely that a path can be,
e.g., either "s:/mypath/..." or "/cygdrive/s/mypath/...". That confusion plus
a missing rule was causing my problems. Thanks for your help, which, even
thought wasn't directly applicable, helped isolate the real problem.
--
Randy Yates
Sony Ericsson Mobile Communications
Research Triangle Park, NC, USA
randy.yates@sonyericsson.com, 919-472-1124