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
We tried to update pyrit for Kali but the build fails on i386, we can reproduce this with 0.4.0 (patched for new scapy) and 0.5.1 (as released). Here's the log of the problem:
This only happens when SSE2 is enabled. When I build with a cpyrit/_cpyrit_cpu.h edited to not define COMPILE_PADLOCK and COMPILE_SSE2, then the problem goes away and the test succeeds.
This also seems to be processor specific as I can't reproduce the problem on my laptop but I can reproduce it on the build server.
In both cases, the build environment is mostly identical as the build happens in a minimal chroot with only the latest version of each required dependency available.
hello,
this bug is currently preventing pyrit (as of version 0.4.0) to be released with the upcoming debian stable release - could you have a look at this somehow urgently? let us know if there is anything Debian can do to help you investigating and fixing this bug
We tried to update pyrit for Kali but the build fails on i386, we can reproduce this with 0.4.0 (patched for new scapy) and 0.5.1 (as released). Here's the log of the problem:
This only happens when SSE2 is enabled. When I build with a cpyrit/_cpyrit_cpu.h edited to not define COMPILE_PADLOCK and COMPILE_SSE2, then the problem goes away and the test succeeds.
This also seems to be processor specific as I can't reproduce the problem on my laptop but I can reproduce it on the build server.
My laptop CPU is:
The build server CPU is:
In both cases, the build environment is mostly identical as the build happens in a minimal chroot with only the latest version of each required dependency available.
The full build log is here if you want to check it:
http://buildd-amd64.kali.org/build-logs/pyrit_0.5.1+git20160815-0kali1-kali-experimental-i386-20170110-150459.3114.log
The text was updated successfully, but these errors were encountered: