Sig fault 11-22

Development
41

Output of this is %PATH% rem does this have to do anything with me using msys mingw terminal?

42

So the build environment ā€œseems to workā€ but doesnā€™t so something is not being ā€œmakeā€ correctly. It may be due to the PATH variable pointing to ā€œolderā€ libraries. I think this might be true as if you have updated pacman then only the environment variables are NOT updated.

43

Elaborate, i have no idea if i updated the vars as itā€™s fresh install of everything related to plugin creation

44 
export RACK_DIR=<Rack SDK folder>
#may have not been set in ./bashrc correctly
#or
echo $PATH
#might be finding some alternative libraries to link to because they are earlier in PATH
which gcc
gcc --version
#checks if the correct gcc is used in case of multiple build tools
#everything else should be ok if instructions followed
45 
Haqz@DESKTOP-M24S23N MINGW64 ~
$ export RACK_DIR=/d/Rack-SDK/

Haqz@DESKTOP-M24S23N MINGW64 ~
$ echo $PATH
/mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

Haqz@DESKTOP-M24S23N MINGW64 ~
$ which gcc
/mingw64/bin/gcc

Haqz@DESKTOP-M24S23N MINGW64 ~
$ gcc --version
gcc.exe (Rev2, Built by MSYS2 project) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE```
46

And just incase

openssl dgst `which gcc`
#for linux gives on my machine. Checking for binary accuracy "virus??"
SHA256(/usr/bin/gcc)= 7633416c7f569942758cbffc9660b1f4b45f0abff0f076ea31b7d964b34cc694
47 
$ openssl dgst `which gcc`
C:/msys64/mingw64/bin/gcc: No such file or directory

Haqz@DESKTOP-M24S23N MINGW64 ~
$ SHA256(/usr/bin/gcc)= 7633416c7f569942758cbffc9660b1f4b45f0abff0f076ea31b7d964b34cc694
bash: syntax error near unexpected token `/usr/bin/gcc'
48

is a literal string.

49

Yeah? What about it

50

It alters the SHA256, so it seems

indicates problems finding the GCC. and it was just running the ā€œoutputā€ I got.

And that also seems that ā€œC:/msys64/ā€ was prepended to the openssl digest commandā€™s filename. This could be because openssl is not installed in the msys64 environment. It would have been ā€œ/c/ā€ prefix if it was an msys64 directory and filename, indicating a windows binary was called.

Iā€™d set up a new msys install and try again.

51

you may have to add the .exe


$ openssl dgst `which gcc`
C:/msys64/mingw64/bin/gcc: No such file or directory

$ openssl dgst `which gcc.exe`
SHA256(C:/msys64/mingw64/bin/gcc.exe)= ddc0bdba9c5169d5546a43786c8d7c2ceecc49baaa65a2e270f3d8e2e3f5374f

$ gcc --version
gcc.exe (Rev2, Built by MSYS2 project) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
52

With that it worked

Haqz@DESKTOP-M24S23N MINGW64 ~
$ openssl dgst `which gcc.exe`
SHA256(C:/msys64/mingw64/bin/gcc.exe)= ddc0bdba9c5169d5546a43786c8d7c2ceecc49baaa65a2e270f3d8e2e3f5374f
53

You are using Msys2, 64 bit, yes?

54

Yes