38
edits
Changes
Jump to navigation
Jump to search
Line 16:
Line 16: − + − − If you do choose you use the WSL and you get the error: − <code> − line *: syntax error near unexpected token `(' − </code> − when running the command − <code> − source ~/.bashrc − </code> − From what I understand it is because you're using a x64 bit of Windows and Bash doesn't understand what a '(' is, you can remedy this by opening the bashrc file in nano or if you want to be "Mr Gangster" you can use vi/vim however I RECOMMEND you use nano. − Once it's open navigate to to the line that has "export PATH=" look for all instances of things referencing files with "Program Files (x86)" in it, make sure the entries are still separated with a ":" though!
Undo revision 20192 by Arefu (talk) Don't set path in .bashrc
** Windows 10 (post-Anniversary Update): Start -> devkitPro -> MSYS
** Windows 10 (post-Anniversary Update): Start -> devkitPro -> MSYS
Alternatively starting with Windows 10 Anniversary Update (Version 1607), the [https://msdn.microsoft.com/en-us/commandline/wsl/install_guide Windows Subsystem for Linux (WSL)] may also be used to run the Linux version of devkitARM. Unless you have some particular need for WSL it's recommended that you stick to a more standard environment.
Alternatively starting with Windows 10 Anniversary Update (Version 1607), the [https://msdn.microsoft.com/en-us/commandline/wsl/install_guide Windows Subsystem for Linux (WSL)] may also be used to run the Linux version of devkitARM. Unless you have some particular need for WSL it's recommended that you stick to a more standard environment.
==Unix-like platforms==
==Unix-like platforms==