-
Notifications
You must be signed in to change notification settings - Fork 254
Don't assume anything above SSE2 when compiling X64 code (e.g. dart binary) #233
Conversation
…inary) Allows users to run flutter tools on old Mac's. Fixes flutter/flutter#24916
|
Sorry - I'm a bit of a newbie --- where can I download the ZIP for this updated code? |
|
@cpalanzo This commit is being rolled into the engine in flutter/engine#8593. From there it will automatically get rolled into the framework once all tests pass. The commit messages made by the bots for such rolls say something like "Roll engine SHA1..SHA2 (n commits)". Once that happens, |
|
I can't use flutter upgrade - since my flutter install doesn't work (that's why I need this build).
===== CRASH ===== |
|
Since I can't use flutter upgrade - I tried again - pulling into a clean directory and using flutter to get dependencies - console log is below ( apologies - still a newbie at this...) but got a CRASH building the flutter tool.... |
|
So this configuration change did not fix the whole problem. Can you enable crash dumps by doing $ ulimit -c unlimited
$ flutter
$ ls -al /cores/
# There should be few core.PID files in /cores directoryThen you should be able to load these cores either in Here you would need to disassemble around the address where crash occurred, e.g. you look at and you disassemble around ABCDEF |
|
|
Actually I took a moment and did the following - not sure at all how to interpret this: |
|
I looked into it a bit more, contrary to what I thought passing |
|
I've got the same problem and followed it through from the previous bug report (#235) Has a fix been rolled out yet? Or is there manual fix? My setup: iMac (mid-2007), El Capitan Flutter installation kit: flutter_macos_v1.5.4-hotfix.2-stable Errors: flutter doctor -v ===== CRASH ===== ===== CRASH ===== |
|
@brianlinuxing |
Allows users to run flutter tools on old Mac's.
Fixes flutter/flutter#24916