I am trying to upgrade the version of GCC
used by our build system for cross compiling Linux applications on Windows. The existing compiler is GCC 4.9.1
and was originally built with crosstool-ng
I have managed to build GCC 9.2.0
using crosstool-ng
in Cygwin
. From within Cygwin
the new cross compiler works correctly.
The existing, older cross-compiler is used from a Windows CMD
shell as part of a SCons
build system. If I try to execute the new cross-compiler from a Windows CMD
I get the following failure:
'['C:\\BuildTools\\gnu_xcompile\\B\\x86_64-unknown-linux-gnu\\bin\\x86_64-unknown-linux-gnu-gcc.exe',
'-v']' returned non-zero exit status 3221225595. in SConstruct
The same error occurs for all the the executables located in the x86_64-unknown-linux-gnu\\bin directory
, which indicates that I am missing something at start-up that allows the Cygwin
exe's to run from a Windows CMD
.
Note: I have added cygwin1.dll
(from the Cygwi
n installation used to build the cross compiler) to the path, without it on the path I get a missing dll error.
The error I am getting is also displayed in a window as:
The application was unable to start correctly (0xc000007b)
Click OK to close the application.
This indicates a compatibility error and is usually the result of running a 32Bit application on newer versions of Windows.
Is there some additional configuration I need to perform to allow running Cygwin executables from a Windows CMD shell?
User contributions licensed under CC BY-SA 3.0