Skip to content

Testing new windows config setup#8092

Draft
xavier2k6 wants to merge 1 commit into
arvidn:RC_2_0from
xavier2k6:windows_new_config
Draft

Testing new windows config setup#8092
xavier2k6 wants to merge 1 commit into
arvidn:RC_2_0from
xavier2k6:windows_new_config

Conversation

@xavier2k6
Copy link
Copy Markdown
Contributor

No description provided.

@xavier2k6 xavier2k6 force-pushed the windows_new_config branch 2 times, most recently from 0ebf647 to c428cd0 Compare December 31, 2025 14:31
@xavier2k6
Copy link
Copy Markdown
Contributor Author

@arvidn Are the sanitizer failures genuine?, can you handle them if they are?

@arvidn
Copy link
Copy Markdown
Owner

arvidn commented Jan 1, 2026

@arvidn Are the sanitizer failures genuine?, can you handle them if they are?

These crashes look more like symptoms of some issue in the build or linking. e.g. if the address sanitizer runtime library can't be found, or something. I would expect msvc's address sanitizer to also print helpful output if there's an actual sanitizer failure.

@xavier2k6
Copy link
Copy Markdown
Contributor Author

Might be time to update the copyright year, last update was 2022 via #6931

@xavier2k6
Copy link
Copy Markdown
Contributor Author

b2 5.4.2+ fixes autodetection of vs2026

https://github.com/bfgroup/b2/releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants