I'm guessing the g++ command for compiling some part of VBA fails, thus resulting in the execution of
rm -f ".deps/GBA.Tpo" (you should be able to confirm that this file is no longer present), followed by
an "exit 1".
Or, you could try running the "sudo make" again, followed right afterwards by
This should show the exit status of the "make" command.
I think this will tell you "1", indicating that the program failed.
If it does, you could try appending something like
Code:
2>&1 >/tmp/compile_errors
to the end of the g++ command. This should capture any output or error messages of g++ into the file /tmp/compile_errors.
Then run a "cat" on that file and post back the error messages...