Replies: 4 comments
-
Please remove this folder,
Then use platform
|
Beta Was this translation helpful? Give feedback.
-
Thanks! That fixed it. However, the build process I had builds for 3 targets platforms (armv7, aarch64, and x86-64, all linux):
It used to produce for all 3 architectures without issues using the --platform flag. |
Beta Was this translation helpful? Give feedback.
-
I don't suppose I need to use export PYARMOR_PLATFORM for each target platform I'm building for? |
Beta Was this translation helpful? Give feedback.
-
The problem is One solution is to obfuscate all the scripts with feature So I suggest you obfuscate the scripts in the any x86-64 platform, it will obfuscate the scripts with feature Please also read this section |
Beta Was this translation helpful? Give feedback.
-
Been using pyarmor for the last couple of years without any issues. Recently, I moved all code to a new machine (Ryzen 5900X) and install QEMU with Debian buster on it with armv7 architecture. This actually did work for a while but today I started receiving all kinds of segmentation faults when running pyarmor.
I purchased pyarmor.
Version: Tried both release (6.7.4) and From Github (6.7.5)
uname -a: Linux workshop 5.13.6-051306-generic #202107291324-Ubuntu SMP Thu Jul 29 13:34:02 UTC 2021 armv7l GNU/Linux
I deleted .pyarmor directory and then ran:
After this, any command (except for pyarmor -h) results in a segmentation fault:
Beta Was this translation helpful? Give feedback.
All reactions