src/minikc/SimkaCountProcess.cpp | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

 separate out array as a defined struct
 Some (newer) GCC throw error when accessing the address of a temporary array, so separate the array as a defined struct to prevent this address issue. 

src/SimkaCount.cpp | 2 1 + 1 - 0 !
src/SimkaMerge.cpp | 2 1 + 1 - 0 !
src/SimkaPotara.cpp | 2 1 + 1 - 0 !
src/SimkaPotara.hpp | 2 1 + 1 - 0 !
src/core/SimkaAlgorithm.cpp | 4 2 + 2 - 0 !
src/core/SimkaCommons.hpp | 2 1 + 1 - 0 !
src/core/main.cpp | 2 1 + 1 - 0 !
src/simkaMin/SimkaMin.cpp | 2 1 + 1 - 0 !
8 files changed, 9 insertions(+), 9 deletions(-)

 display more information in caught errors
 The errors are unmarked and understanding the originating source file is not easy, so append the file names and other diagnostic information before the error messages. Do not apply this patch when uploading.

src/SimkaPotara.cpp | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 hard code binary path
 Simka gets the "simka" binary path from the command "simka", which is not the same as /usr/bin/simka. Hard code this path so that simka finds its binary.

example/simple_test.sh | 11 1 + 10 - 0 !
tests/simkaMin/test_simkaMin.py | 34 17 + 17 - 0 !
tests/simple_test.py | 12 6 + 6 - 0 !
3 files changed, 24 insertions(+), 33 deletions(-)

 modify the test python files to use binaries in /usr/bin

simkaMin/simkaMin.py | 6 3 + 3 - 0 !
simkaMin/simkaMin_update.py | 6 3 + 3 - 0 !
tests/simple_test.py | 2 1 + 1 - 0 !
3 files changed, 7 insertions(+), 7 deletions(-)

 port over python files using python2 to python3

CMakeLists.txt | 24 16 + 8 - 0 !
1 file changed, 16 insertions(+), 8 deletions(-)

 use system-wide debian packaged libraries instead
 This is instead of relying on cmake to compile and link against the libraries included within simka

tests/simple_test.py | 26 13 + 13 - 0 !
1 file changed, 13 insertions(+), 13 deletions(-)

 run tests on a single core
 On very high cores count machines, simka may deadlock if left to using as many
 threads as there are cores available.  Parallel runs are kept for tests which
 explicitly test the parallel aspect of the program.
 .
 Additional flush=True are for better readability of the autopkgtest output.