You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the setup or "run me" script fails to set the environment variables CC, CXX and MINGW_HOME to their respective locations in the MinGW64 folder that MSYS creates during the initial setup.
This results in errors such as:
Where it cannot find the GCC binary, G++ binary or other MinGW locations.
In this particular example, they were referring to a location on my C drive, the default install location of MinGW.
pm3 ~/proxmark3$ set
[...]
CC=C:/MinGW/bin/gcc.exe
CXX=C:/MinGW/bin/g++.exe
MINGW_HOME=C:/MinGW/
[...]
This would've worked if MinGW was installed there. Mine wasn't, which revealed this problem.
The solution would be to use the same relative paths or variable based paths as the makefile script does, where it assigns these variables relative to the ProxSpace "home" (msys folder)
In my case, this was done by setting them from the terminal:
It seems that the setup or "run me" script fails to set the environment variables CC, CXX and MINGW_HOME to their respective locations in the MinGW64 folder that MSYS creates during the initial setup.
This results in errors such as:
Where it cannot find the GCC binary, G++ binary or other MinGW locations.
In this particular example, they were referring to a location on my C drive, the default install location of MinGW.
This would've worked if MinGW was installed there. Mine wasn't, which revealed this problem.
The solution would be to use the same relative paths or variable based paths as the makefile script does, where it assigns these variables relative to the ProxSpace "home" (msys folder)
In my case, this was done by setting them from the terminal:
Although these are clearly absolute paths meant to be used in the environment set up by MSYS.
The text was updated successfully, but these errors were encountered: