Skip to content

Don't use -z,defs linker flag when building shared libraries with emscripten #123396

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

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

mcbarton
Copy link
Contributor

A project called CppInterOp makes use of llvm. When doing emscripten builds we get a warning that -Wl,-z,defs is not recognised (see
https://github.com/compiler-research/CppInterOp/actions/runs/12812649594/job/35724827621#step:9:214 ). It was determined that this flag was coming from here.

Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the cmake Build system in general and CMake in particular label Jan 17, 2025
Copy link
Contributor

@vgvassilev vgvassilev left a comment

Choose a reason for hiding this comment

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

Perhaps @sbc100 is one of the people who could tell if that makes sense...

@vgvassilev vgvassilev requested a review from sbc100 January 17, 2025 21:10
Copy link

⚠️ We detected that you are using a GitHub private e-mail address to contribute to the repo.
Please turn off Keep my email addresses private setting in your account.
See LLVM Discourse for more information.

@mcbarton
Copy link
Contributor Author

@sbc100 Are you able to review this PR for me?

@sbc100 sbc100 changed the title Remove -Wl,-z,defs linker flag when building shared libraries using llvm with emscripten Remove -Wl,-z,defs linker flag when building shared libraries with emscripten Jan 28, 2025
@sbc100 sbc100 changed the title Remove -Wl,-z,defs linker flag when building shared libraries with emscripten Don't use -z,defs linker flag when building shared libraries with emscripten Jan 28, 2025
@sbc100 sbc100 merged commit 3cfda4f into llvm:main Jan 28, 2025
8 checks passed
Copy link

@mcbarton Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as the builds can include changes from many authors. It is not uncommon for your change to be included in a build that fails due to someone else's changes, or infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself. This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmake Build system in general and CMake in particular
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants