`“apue.h”`is not a global environment PATH , but program can retrieve it
up vote
0
down vote
favorite
I am learning from APUE3e
#include "apue.h"
#include <dirent.h>
int main(int argc, char *argv)
{
DIR *dp;
struct dirent *dirp;
....
In the header, import a user-definded module "apue.h"
. the program run correctly after compiled.
The apue.h
is placed in /Library/Developer/CommandLineTools/usr/include
,
What confuse me is that /Library/Developer/CommandLineTools/usr/include
is not in the $PATH but could be retrieved by the program globally.
$ echo $PATH | grep include
#does not return anything.
How could the program get it done?
c
add a comment |
up vote
0
down vote
favorite
I am learning from APUE3e
#include "apue.h"
#include <dirent.h>
int main(int argc, char *argv)
{
DIR *dp;
struct dirent *dirp;
....
In the header, import a user-definded module "apue.h"
. the program run correctly after compiled.
The apue.h
is placed in /Library/Developer/CommandLineTools/usr/include
,
What confuse me is that /Library/Developer/CommandLineTools/usr/include
is not in the $PATH but could be retrieved by the program globally.
$ echo $PATH | grep include
#does not return anything.
How could the program get it done?
c
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am learning from APUE3e
#include "apue.h"
#include <dirent.h>
int main(int argc, char *argv)
{
DIR *dp;
struct dirent *dirp;
....
In the header, import a user-definded module "apue.h"
. the program run correctly after compiled.
The apue.h
is placed in /Library/Developer/CommandLineTools/usr/include
,
What confuse me is that /Library/Developer/CommandLineTools/usr/include
is not in the $PATH but could be retrieved by the program globally.
$ echo $PATH | grep include
#does not return anything.
How could the program get it done?
c
I am learning from APUE3e
#include "apue.h"
#include <dirent.h>
int main(int argc, char *argv)
{
DIR *dp;
struct dirent *dirp;
....
In the header, import a user-definded module "apue.h"
. the program run correctly after compiled.
The apue.h
is placed in /Library/Developer/CommandLineTools/usr/include
,
What confuse me is that /Library/Developer/CommandLineTools/usr/include
is not in the $PATH but could be retrieved by the program globally.
$ echo $PATH | grep include
#does not return anything.
How could the program get it done?
c
c
asked Nov 10 at 11:03
avirate
647113
647113
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
$PATH
is where the shell looks for executables, not header files. This answer shows how you can get the compiler to show you where it's looking for header files.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
$PATH
is where the shell looks for executables, not header files. This answer shows how you can get the compiler to show you where it's looking for header files.
add a comment |
up vote
1
down vote
accepted
$PATH
is where the shell looks for executables, not header files. This answer shows how you can get the compiler to show you where it's looking for header files.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
$PATH
is where the shell looks for executables, not header files. This answer shows how you can get the compiler to show you where it's looking for header files.
$PATH
is where the shell looks for executables, not header files. This answer shows how you can get the compiler to show you where it's looking for header files.
answered Nov 10 at 11:05
Bruce Collie
4005
4005
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238288%2fapue-his-not-a-global-environment-path-but-program-can-retrieve-it%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown