-
Notifications
You must be signed in to change notification settings - Fork 37.7k
depends: update LD64_VERSION
to 711
#28630
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
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
LD64_VERSION
to 711 LD64_VERSION
to 711
Damn, should have caught this :( |
Why not derive the
|
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.
ACK 092daa2
That would prevent us from being able to set it to anything other than the exact value output by -v. Also unsure if whatever parsing code you write would also be compatible with lld. |
The test passes with the first commit been reverted. |
The because if unset, the value is the default linker version, iirc. |
How is it unset? |
If the test is still passing, clearly it's not being set to 609. Otherwise it would fail. |
Please consider https://github.com/hebasto/bitcoin/tree/pr28630/1011. the
but the Guix build succeeds:
|
We don't need another branch. I'm saying the same thing. If the test is passing, clearly the value in the binary is not being set to 609 (in which case, it's being set to the default linker value (711)). (which is why the test is passing with the 2nd commit reverted). |
If code has |
To check for the version being used/embedded? Clearly it's exposed a bug here, potentially in our understanding of |
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.
ACK 092daa2.
Suggesting to drop "Add a test so it's impossible to forget." from the PR description before merging.
Clearly it's exposed a bug here, potentially in our understanding of
-mlinker-version
.
Agree.
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.
ACK 092daa2
i dont know about mac linker specifics but reviewed symbol-check.py change and lgtm
GUIX hashes
|
ACK 092daa2 |
092daa2 contrib: add test for macOS linker version to symbol-check (fanquake) cefbf0b depends: update LD64_VERSION to 711 (fanquake) Pull request description: I forgot to do this in bitcoin@7d58152. Add a test so it's impossible to forget. ACKs for top commit: TheCharlatan: utACK 092daa2 achow101: ACK 092daa2 jarolrod: ACK 092daa2 hebasto: ACK 092daa2. laanwj: ACK 092daa2 Tree-SHA512: 37f0bdfd6607a7760eabe5efe279532ba0c59c0915161e08d5e3b9a0b7705839d62537d6e17406062f6a0a1db5407575da7cd671e9cb916e422e77f5649c6e2b
I forgot to do this in 7d58152.
Add a test so it's impossible to forget.