What is my Include Path

sysbox · 10-05-2009, 05:10 PM

I'm logging into a somewhat public RedHat system and I'm using tcsh as my default shell. I don't know what directories the local system admins added to my Include path.

When I compile a code, it finds Whatever.h, and I can't tell where it is coming from. How can I determine what the Include path is, and where it is set?

lutusp · 10-05-2009, 05:42 PM

Quote:

Originally Posted by sysbox

I'm logging into a somewhat public RedHat system and I'm using tcsh as my default shell. I don't know what directories the local system admins added to my Include path.

When I compile a code, it finds Whatever.h, and I can't tell where it is coming from. How can I determine what the Include path is, and where it is set?

Code:

$ whereis Whatever.h

Also, set your own include path. Don't accept someone else's.

sysbox · 10-05-2009, 05:53 PM

That isn't working.

Code:

> whereis Whatever.h
Whatever:

>Also, set your own include path. Don't accept someone else's.

Okay. How do I determine what someone else's include path is, and how do I set my own include path?

John VV · 10-05-2009, 07:12 PM

for starters

Code:

echo $PATH

and see what is in the normal system path

sysbox · 10-06-2009, 01:01 PM

I was able to accomplish this with the "whereis" command as lutusp recommended. Actually, that's useful for locating libraries too, which is another problem I've been looking to solve.

So, Thanks for all the help!

lutusp · 10-06-2009, 01:47 PM

Quote:

Originally Posted by sysbox

That isn't working.

Code:

> whereis Whatever.h
Whatever:

But it was your hypothetical example! Replace "Whatever.h" (your example) with a real file name.

sysbox · 10-06-2009, 02:01 PM

Yes, I know that. I was using "whereis" on the real name of the include file I was looking for. The problem was that that include file didn't exist anywhere on my "Include Path", and I didn't know that. So, that's why the whereis output didn't help me much. Actually, it would be nice if whereis explicity stated that it couldn't find the file, but that's okay. Now I know.

Thanks again.

lutusp · 10-06-2009, 06:01 PM

Quote:

Originally Posted by sysbox

Yes, I know that. I was using "whereis" on the real name of the include file I was looking for. The problem was that that include file didn't exist anywhere on my "Include Path", and I didn't know that. So, that's why the whereis output didn't help me much. Actually, it would be nice if whereis explicity stated that it couldn't find the file, but that's okay. Now I know.

Thanks again.

Okay, there's one more thing to try:

$ locate (filename)

If this fails, try this:

# updatedb (takes a while)

Then repeat the locate command.

If all this fails, you really don't have the target file.