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

mpy-cross broken on macOS Mojave #4455

Open
annejan opened this Issue Feb 1, 2019 · 5 comments

Comments

Projects
None yet
5 participants
@annejan
Copy link

annejan commented Feb 1, 2019

It compiles fine, but won't run

./mpy-cross 
dyld: malformed mach-o image: missing LC_DYSYMTAB
Abort trap: 6

I have tried not stripping by removing ,-dead_strip from the Makefile to no avail . .

 ./mpy-cross 
Killed: 9

NB: This is not the same issue as #2941 since this is on the current master.

@annejan annejan changed the title mpy-cross broken on macOS Mohave mpy-cross broken on macOS Mojave Feb 1, 2019

@tannewt

This comment has been minimized.

Copy link

tannewt commented Feb 2, 2019

Try removing binutils that brew installs. I think that was the issue for me.

@dpgeorge

This comment has been minimized.

Copy link
Contributor

dpgeorge commented Feb 3, 2019

I'd suggest this could be related to #3637 : maybe the ABI is different and the NLR code doesn't work.

@andrewleech

This comment has been minimized.

Copy link
Contributor

andrewleech commented Feb 5, 2019

Out of interest, would you mind trying the latest master osx binary from my CI build of mpy-cross?
osx binary:
https://gitlab.com/alelec/mpy_cross/-/jobs/156257348/artifacts/file/mpy-cross

pip install-able copy:
https://gitlab.com/alelec/mpy_cross/-/jobs/155326779/artifacts/file/mpy_cross-1.11.dev45+g67689bfd7-py2.py3-none-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl

I don't have access to a new enough mac to test these on myself.

@Anton-2

This comment has been minimized.

Copy link
Contributor

Anton-2 commented Feb 6, 2019

Tested with the latest Mojave (macOS 10.14.3), and up to date command line tools :

  • The version from your gitlab works ...
    and
  • The version build from a fresh git clone works too.
@andrewleech

This comment has been minimized.

Copy link
Contributor

andrewleech commented Feb 6, 2019

Great to hear on both counts, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment