%% [EMAIL PROTECTED] (Paul Jarc) writes: pj> "Paul D. Smith" <[EMAIL PROTECTED]> wrote:
>> Try using the -p option. That will print make's entire internal >> database and you should be able to find it there. pj> Ok, it appears just before <command-line> in several dependency lists, pj> and also: pj> # Not a target: pj> <built-in>: pj> # Implicit rule search has been done. pj> # File does not exist. pj> # File has not been updated. This means that this file was mentioned only as a prerequisite, but never defined as a target. pj> The Makefile doesn't do any includes, and doesn't contain <built-in>, pj> so this is coming from make internally, right? No. First, make never has anything like that; the only reference to "built-in" in the GNU make source code is "(built-in)" (note parens) and is only in comment output, never as a target or prerequisite. If you do something like this: $ make -pf/dev/null you'll see GNU make's entire built-in database. Looking at the -p output I can see where this is used: sv.o: /package/host/localhost/gcc/lib/gcc-lib ... <built-in> <command line> EXTERN.h av.h c ... etc. I don't know where these are coming from, but they're not coming from any kind of GNU make builtin information. Are you sure you don't have MAKEFILES set or some other odd thing? Look for where the sv.o prerequisites are defined and see if you can see anything there. -- ------------------------------------------------------------------------------- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.org/gmake/ "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make
