Skip to content
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

Fix linking to shared LLVM. #5308

Merged
merged 5 commits into from
Oct 2, 2020
Merged

Fix linking to shared LLVM. #5308

merged 5 commits into from
Oct 2, 2020

Conversation

alexreinking
Copy link
Member

Apparently, LLVM's own llvm_map_components_to_libnames function is busted if you build only the shared library version.

This PR should fix that up and avoid calling this function when shared LLVM is requested.

We should backport this to 10.0.0 for future Deb packaging, and we probably need to add buildbot testing of shared and bundled scenarios. Maybe just the x64 linux bot can run the generator tests.

Fixes #5304.

@alexreinking alexreinking added backport me This change should be backported to release versions build Issues related to building Halide and with CI labels Sep 30, 2020
@alexreinking alexreinking added this to the v10.0.1 milestone Sep 30, 2020
Copy link
Contributor

@steven-johnson steven-johnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but I think we need explicit comment added somewhere about why this is needed (eg "LLVM's own llvm_map_components_to_libnames function is busted if you build only the shared library version")

dependencies/llvm/CMakeLists.txt Show resolved Hide resolved
@alexreinking
Copy link
Member Author

LGTM but I think we need explicit comment added somewhere about why this is needed (eg "LLVM's own llvm_map_components_to_libnames function is busted if you build only the shared library version")

Done. Added the comment inside the if(Halide_SHARED_LLVM) branch.

@steven-johnson
Copy link
Contributor

Does this need to run on the buildbots?

@alexreinking
Copy link
Member Author

Does this need to run on the buildbots?

Yes, for sure

@alexreinking
Copy link
Member Author

Any idea why the buildbots aren't running on this?

@steven-johnson
Copy link
Contributor

Buildbots are very backed up after changes yesterday -- are they pending?

@steven-johnson
Copy link
Contributor

Failure is unrelated, landing

@steven-johnson steven-johnson merged commit ac56ec9 into master Oct 2, 2020
@steven-johnson steven-johnson deleted the build/shared-llvm-fix branch October 2, 2020 16:56
alexreinking pushed a commit that referenced this pull request Oct 16, 2020
@alexreinking alexreinking removed the backport me This change should be backported to release versions label Oct 16, 2020
alexreinking pushed a commit that referenced this pull request Oct 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues related to building Halide and with CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression of issue #5015
2 participants