-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 bb-install
naming conventions, add hashes
#30535
Conversation
I'm using BB for wasm-compatible LLVM binaries. After the original bb-install PR, it started failing with:
and even with this, I get:
The relevant Make.user entries are:
|
@Keno the meaning of the flags has changed a bit, try this instead on this branch:
|
I have added windows versions of OpenBLAS v0.3.3; I had to dodge a compiler bug in AVX-512 register placement. Let's see if Appveyor is happier about that. |
Looks like it's working; we're certainly better off than we were before. There is a single failing test (SuiteSparse LU decomposition) on linux64, (mac64 and linux32 are both fine....) but I'm inclined to merge this and see if that error continues. I've restarted the linux64 build just to see if it magically disappears, but regardless I think this is ready to merge. |
This only adds checksums for darwin, should we have checksums for all/any architecture? Maybe it is better to download a checksum file and use that instead? |
Anything blocking merging this to get AV back? |
I'm going to add checksums for all the architectures and then we can merge. |
Quote to avoid bash freaking out from spurious `)` from compilers that have fancy version strings such as `(Red Hat 7.3.1-5)`, which gets `lastword`'ed down to `7.3.1-5)`.
4d1fb54
to
d4064f6
Compare
Alright this is now good to go from my perspective. As soon as this returns green (the only reason it wouldn't be green is if one of the hashes that I added is wrong) let's merge it. |
That's enough green for me (excluding SuiteSparse LU factorization error). Merging. |
* Fix `bb-install` naming conventions, add hashes * Set `DEP_LIBS` to include `openblas` on Appveyor * When guessing BB libc, default to `glibc` on Linux * Fix bb-install bash parsing failure Quote to avoid bash freaking out from spurious `)` from compilers that have fancy version strings such as `(Red Hat 7.3.1-5)`, which gets `lastword`'ed down to `7.3.1-5)`. * Add `contrib/refresh_bb_tarballs.sh` to aid in batch-grabbing BB hashes (cherry picked from commit 8b189ec)
* Fix `bb-install` naming conventions, add hashes * Set `DEP_LIBS` to include `openblas` on Appveyor * When guessing BB libc, default to `glibc` on Linux * Fix bb-install bash parsing failure Quote to avoid bash freaking out from spurious `)` from compilers that have fancy version strings such as `(Red Hat 7.3.1-5)`, which gets `lastword`'ed down to `7.3.1-5)`. * Add `contrib/refresh_bb_tarballs.sh` to aid in batch-grabbing BB hashes (cherry picked from commit 8b189ec)
Not sure why this should go into 1.0. Removing for now. |
Yeah, I don't know why I added that label. |
@vtjnash here are the changes requested in the original
bb-install
PR.