"Sanju" <[EMAIL PROTECTED]> writes:
> > You didn't show the command that make ran before you got this, but it must
> > have been something like:
> >
> > make -f config/
> >
> > This, of course, is not a valid command line.
>
> like
> $make
>
> OR
> $make -f Makefile
>
> In both cases I get the same error...........I dont understand why its
> complaining for "config/"
I already explained why it's complaining: it's trying to read config/ as a
makefile. There's absolutely no question about that: the error messages
are irrefutable on this point.
The question is "why" (or "where")?
Note when I say "the command line" I don't necessarily mean the command
that you type into the shell. Most makefile environments are recursive,
which means one makefile is invoking another instance of make. It's quite
possible that you're using a variable that isn't properly assigned. For
example, something like this:
SUBMAKE = subdir.mk
recurse:
$(MAKE) -f config/$(SUMAKE)
would do it.
If you're not using "make -f config/" then maybe you're trying to "include"
it? Again, this would be because of a variable that was mistyped or
something:
SUBMAKE = subdir.mk
include config/$(SUMAKE)
or something like that.
Sorry, but you'll just have to turn on debugging, etc. and try to figure
this out. With only the context you've provided there's nothing more we
can do to help.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
_______________________________________________
help-gnu-utils mailing list
help-gnu-utils@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-utils
