~/.bashrc does not recognize export
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
This is probably the weirdest thing you've ever seen. But it's true. I'm on macOS, and want to install devKitARM. After installing Git, the guide told me to show the program where the binaries are. It told me to execute:
echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc
echo "export DEVKITARM=/opt/devkitpro/devkitARM" >> ~/.bashrc
source ~/.bashrc
However, when I do this, it gives me
export: Command not found.
export: Command not found.
export: Command not found.
I looked in the ~/.bashrc and realized that there was already an export PATH command in there, probably for some system function. However, this was not being recognized the entire time. Can someone help?
bash osx bashrc
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
add a comment |Â
up vote
3
down vote
favorite
This is probably the weirdest thing you've ever seen. But it's true. I'm on macOS, and want to install devKitARM. After installing Git, the guide told me to show the program where the binaries are. It told me to execute:
echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc
echo "export DEVKITARM=/opt/devkitpro/devkitARM" >> ~/.bashrc
source ~/.bashrc
However, when I do this, it gives me
export: Command not found.
export: Command not found.
export: Command not found.
I looked in the ~/.bashrc and realized that there was already an export PATH command in there, probably for some system function. However, this was not being recognized the entire time. Can someone help?
bash osx bashrc
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
2
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
2
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing likecat,cpandls?  These are not bash commands.  What happens if you just typeexportat your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Sep 26 '17 at 1:58
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
This is probably the weirdest thing you've ever seen. But it's true. I'm on macOS, and want to install devKitARM. After installing Git, the guide told me to show the program where the binaries are. It told me to execute:
echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc
echo "export DEVKITARM=/opt/devkitpro/devkitARM" >> ~/.bashrc
source ~/.bashrc
However, when I do this, it gives me
export: Command not found.
export: Command not found.
export: Command not found.
I looked in the ~/.bashrc and realized that there was already an export PATH command in there, probably for some system function. However, this was not being recognized the entire time. Can someone help?
bash osx bashrc
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
This is probably the weirdest thing you've ever seen. But it's true. I'm on macOS, and want to install devKitARM. After installing Git, the guide told me to show the program where the binaries are. It told me to execute:
echo "export DEVKITPRO=/opt/devkitpro" >> ~/.bashrc
echo "export DEVKITARM=/opt/devkitpro/devkitARM" >> ~/.bashrc
source ~/.bashrc
However, when I do this, it gives me
export: Command not found.
export: Command not found.
export: Command not found.
I looked in the ~/.bashrc and realized that there was already an export PATH command in there, probably for some system function. However, this was not being recognized the entire time. Can someone help?
bash osx bashrc
bash osx bashrc
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
edited Sep 26 '17 at 7:40
Kusalananda
106k14209327
106k14209327
asked Sep 25 '17 at 23:21
SirNapkin1334
182
asked Sep 25 '17 at 23:21
SirNapkin1334
182
asked Sep 25 '17 at 23:21
SirNapkin1334
182
182
2
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
2
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing likecat,cpandls?  These are not bash commands.  What happens if you just typeexportat your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Sep 26 '17 at 1:58
add a comment |Â
2
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
2
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing likecat,cpandls?  These are not bash commands.  What happens if you just typeexportat your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.
– Scott
Sep 26 '17 at 1:58
2
2
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
2
2
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing like
cat, cp and ls?  These are not bash commands.  What happens if you just type export at your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Sep 26 '17 at 1:58
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing like
cat, cp and ls?  These are not bash commands.  What happens if you just type export at your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Sep 26 '17 at 1:58
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
Your currently running shell is the (TENEX) C shell, which does not have an export command. You cannot source a Bourne Again or POSIX shell script in the C shells. The C shell syntax is different to the Bourne/POSIX shell syntax.
Adding these environment variables to your interactive shell involves the C shell's setenv command. Having this done automatically for login shells involves the C shell's ~/.login script.
The manual installation instructions actually simply say "Add these variables in your execution environment". The Bourne Again shell is just a "for instance". Obviously, if you aren't using the Bourne Again shell, which you clearly are not, then you do what is appropriate for your actual choice of shell.
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
Your currently running shell is the (TENEX) C shell, which does not have an export command. You cannot source a Bourne Again or POSIX shell script in the C shells. The C shell syntax is different to the Bourne/POSIX shell syntax.
Adding these environment variables to your interactive shell involves the C shell's setenv command. Having this done automatically for login shells involves the C shell's ~/.login script.
The manual installation instructions actually simply say "Add these variables in your execution environment". The Bourne Again shell is just a "for instance". Obviously, if you aren't using the Bourne Again shell, which you clearly are not, then you do what is appropriate for your actual choice of shell.
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
add a comment |Â
up vote
5
down vote
accepted
Your currently running shell is the (TENEX) C shell, which does not have an export command. You cannot source a Bourne Again or POSIX shell script in the C shells. The C shell syntax is different to the Bourne/POSIX shell syntax.
Adding these environment variables to your interactive shell involves the C shell's setenv command. Having this done automatically for login shells involves the C shell's ~/.login script.
The manual installation instructions actually simply say "Add these variables in your execution environment". The Bourne Again shell is just a "for instance". Obviously, if you aren't using the Bourne Again shell, which you clearly are not, then you do what is appropriate for your actual choice of shell.
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
Your currently running shell is the (TENEX) C shell, which does not have an export command. You cannot source a Bourne Again or POSIX shell script in the C shells. The C shell syntax is different to the Bourne/POSIX shell syntax.
Adding these environment variables to your interactive shell involves the C shell's setenv command. Having this done automatically for login shells involves the C shell's ~/.login script.
The manual installation instructions actually simply say "Add these variables in your execution environment". The Bourne Again shell is just a "for instance". Obviously, if you aren't using the Bourne Again shell, which you clearly are not, then you do what is appropriate for your actual choice of shell.
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
Your currently running shell is the (TENEX) C shell, which does not have an export command. You cannot source a Bourne Again or POSIX shell script in the C shells. The C shell syntax is different to the Bourne/POSIX shell syntax.
Adding these environment variables to your interactive shell involves the C shell's setenv command. Having this done automatically for login shells involves the C shell's ~/.login script.
The manual installation instructions actually simply say "Add these variables in your execution environment". The Bourne Again shell is just a "for instance". Obviously, if you aren't using the Bourne Again shell, which you clearly are not, then you do what is appropriate for your actual choice of shell.
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
answered Sep 26 '17 at 3:52
JdeBP
29.3k460136
29.3k460136
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
add a comment |Â
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
See also this SO question about how to change login shell on macOS: stackoverflow.com/questions/453236/…
– Kusalananda
Sep 26 '17 at 7:45
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
Thanks! I figured out I had to run the terminal as bash, then source the /.bashrc
– SirNapkin1334
Sep 26 '17 at 23:41
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f394430%2fbashrc-does-not-recognize-export%23new-answer', 'question_page');
);
Post as a guest
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
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
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
2
Are you sure that you’re running bash?
– Scott
Sep 26 '17 at 1:09
I should be... I'm pretty sure it's pre-installed on macOS, and other bash commands work. Also, oddly, the man page for it exists, but the command itself not.
– SirNapkin1334
Sep 26 '17 at 1:40
2
(1) “it's pre-installed†— proves nothing. (2) “other bash commands work†— what do you mean?  Are you talking about thing like
cat,cpandls?  These are not bash commands.  What happens if you just typeexportat your command prompt? (3) “the man page for it exists†— the man page for what? (4) “the command itself not†— what do you mean? Please do not respond in comments; edit your question to make it clearer and more complete.– Scott
Sep 26 '17 at 1:58