-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ARM v6 is not supported on 1.13 and 1.14 #25562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I used the test from #24855 Here is what happens on my pi zero pi@pizero:~/testdart $ ulimit -c unlimited # to allow core to be generated pi@pizero:~/testdart $ ../dart-sdk-d/bin/pub get -v pi@pizero:~/testdart $ gdb /home/pi/dart-sdk-d/bin/dart core |
Disabling the hand-coded assembly in boringssl makes the crash during pub get go away. https://codereview.chromium.org/1613233006/ In a case like this, where the fix isn't obvious, I'm not sure that trying to find and upstream a fix for the hand-coded assembly is the right thing to do. We should rather file a bug with the boringssl authors. |
@sebe If you're set up to do a build for Pi0, could you give this fix a try? Thanks! |
/cc @danrubel |
applied the patch to third_party/boringssl/boringssl_configurations.gypi |
You'd also need the first of the two patches above, and to pass |
Cool, -a armv6 is not a option for my build.py, so I just changed it to Dart_arm_Base from Dart_armv6_Base in the patch and pub get works fine now. |
This crash has been fixed on bleeding edge by the two CLs above. |
Dart versions after 1.12 have a segfault when built for ARM v6. A hello world program works fine, but pub get fails.
The most likely candidate is the switch from NSS to BoringSSL. It would be good if people could verify that a program using secure sockets fails, and others don't. There are also variables that can be set in the gyp files, to build a Dart VM without BoringSSL or secure networking support.
It is listed in our FAQ that we support ARM v6, and the Rasberry pi one and zero use it, I think.
So we need to decide what to do about this. There is also an issue on ARM64 support, which is just waiting on a roll of BoringSSL to a more recent version #24321
@sgjesse @mit-mit @zanderso
The text was updated successfully, but these errors were encountered: