-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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 #17523 - Resolve internal symbols referenced from the PLT ##bin #23805
base: master
Are you sure you want to change the base?
Conversation
@trufae The build ('sys/install.sh') fails with:
|
I think the fix for the compile error is to replace
|
doesnt seems to break anything. but .. @grgalex it is improving anything? maybe we should have a test for this before merging :? |
@trufae I think there are still commits missing from this PR. In the issue (#17523), GitHub shows multiple commits referencing the issue. Some of them may be duplicates, while others implement a distinct part of the fix. This PR only contains (the updated equivalent) of d98edd0. All commits in the list from the issue are telling are part of the same story, namely:
Right now, with the commit that this PR has, we don't set the value of the So, we need to apply all those commits in order to get the final proposed change. As it is right now, with the missing content, the PR can't fix the problem :( |
What do you think is the smoothest way to fix this? (Btw, I think this happened because the PR branch was deleted and we forgot to merge, so now all we have of it are a bunch of lonely commits) |
I would suggest you to create a PR with the patches you mention and squash/rebase them to make it work, testing them in local and waiting for the CI, adding more tests will be good too. Which is the PR that wasn't merged? I guess the PR was closed because of conflicts and not clearly fixing the problem, but if you can fix #21117 |
FOUND IT! This is your original PR that was never merged, and whose branch was deleted. It's a single commmit too! So, in essence, the present PR (#23805) should have picked the commit from #21708 instead of the one it has now :) I think it should be very straightforward for you to do this and force-push to this branch. |
Description