-
Notifications
You must be signed in to change notification settings - Fork 109
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
Use old ld64 linker on MacOS >= 15.0 #1083
Conversation
pytensor/link/c/cmodule.py
Outdated
# XCode15 introduced ld_prime linker. At the time of writing, this linker | ||
# leads to multiple issues, so we supply a flag to use the older dynamic | ||
# linker: ld64 | ||
cxxflags.append("-ld64") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this back compatible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’ll have to add a platform version check to add this flag or not
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1083 +/- ##
==========================================
- Coverage 82.10% 82.10% -0.01%
==========================================
Files 183 183
Lines 47930 47932 +2
Branches 8633 8634 +1
==========================================
+ Hits 39354 39355 +1
Misses 6410 6410
- Partials 2166 2167 +1
|
@ricardoV94, I patched this |
Description
Add a flag to use Mac's older
ld64
linker instead of the newld_prime
linker. This might be the underlying cause of the problems that are still coming out of #1005. These issues show thatpytensor
fails in its compilation phase. The exception is a bit masked, but it seems to indicate that the linker had problems and exited with a signal. In my case it was a segfault with signal 11. I've seen other cases that seem similar and complain about symbols that should be defined in libtapi.dylib. The problem is that I can't reproduce in this isolated environment. My attempt to check whether this problem exists on Mac was to bump the version of the macos runner to 15 (the bump was supposed to happen during december anyway).Related Issue
Checklist
Type of change
📚 Documentation preview 📚: https://pytensor--1083.org.readthedocs.build/en/1083/