[wplug] Very strange problem

[Dave Neuer]

#include <netinet/ip.h> is the canonical form, unless
your system has some wacky idea about the standard
include path.

Which, I'm not sure how to determine; gcc
-print-search-dirs will show you where is looks for
libraries, but not header files (on unix it's
traditionally been /usr/include, but there's probably
a way to specify it when building gcc; if that's
messed up, then it makes sense that you'd have
problems).

Dave

--- Hagbard Celine <hceline at softhome.net> wrote:
> I tried `#include "/usr/include/netinet/ip.h"',
> and...
> 
> Son of a Cocker Spaniel, if it didn't work!!
> 
> Okay, I suppose the next question is:  Where do the
> angle brackets get expanded
> to the include path?  Perhaps something went bufu in
> the specification of the
> include path?
> 
> Hagbard
> > 
> > you could always try specifying an abslute path to
> ip.h
> > 
> > sounds to me like maybe there's another
> netinet/ip.h path on your sys that's being used? 
> not likely, but it sure sounds like it--and the one
> it's using doesn't have those things def'd.  could
> be why renaming it to something unique--while still
> in the same relative path spec--results in proper
> inclusion.  might be something to try.
> > 
> > #include </usr/include/netinet/ip.h
> > _______________________________________________
> > wplug mailing list
> > wplug at wplug.org
> > http://www.wplug.org/mailman/listinfo/wplug
> > 
> 
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com