Keith Owens scripsit: > In order to do separate source and object correctly, kbuild 2.5 > enforces the rule that #include "" comes from the local directory, > #include <> comes from the include path. include/linux/zlib.h > incorrectly does #include "zconf.h" instead of #include <linux/zconf.h>, > breaking the rules.
This is not the standard gcc behavior, however; quoted-includes can come from the include path, although the current directory is searched first. The purpose of <>-includes is to suppress searching the current directory. -- John Cowan <[EMAIL PROTECTED]> http://www.reutershealth.com I amar prestar aen, han mathon ne nen, http://www.ccil.org/~cowan han mathon ne chae, a han noston ne 'wilith. --Galadriel, _LOTR:FOTR_ _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
