Fwd: Re: include path problems, or cons vs. make incompatability?

[Brian O'Keefe]

OK, so David points out below that the tilde expansion is bad. I changed it 
to be fully-qualified (-I/home/okeefe/src/dirA) and that truly does change 
things. However, now it appears to be the opposite problem. Now, my compile 
is failing to use /usr/include/netdb.h when myfile.c does the include for 
<netdb.h> (without the rpc/ in front of it).  In this case, I DO want it to 
use the standard header file.

I'll assume that I'm doing something wrong again, but now what?


> To: "Brian O'Keefe" <address@hidden>
> Subject: Re: include path problems, or cons vs. make incompatability?
> Date: Fri, 23 Feb 2001 16:05:57 -0500
> From: David Sanderson <address@hidden>
>
> | So, does cons work differently than make in this respect, or do I just have
> | cons set up incorrectly? Here is the output from my cons attempt:
> |
> | gcc -D_POSIX_SOURCE -DUSE_INTTYPES -DNO_T_TYPES -Iexport/linux/include
> | -I~/src/dirA -c export/linux/src/dirA/rpc/myfile.c -o
>
> I don't know if this is your problem, but this is wrong:  There is no
> directory named '~'. Find whatever is sticking the '~' in there use a
> directory name instead.  Tilde expansion is done by the shell; the
> kernel has no idea what it is supposed to mean.  Cons might not be using
> the shell at all...


Brian O'Keefe
Spinnaker Networks
address@hidden