-
Notifications
You must be signed in to change notification settings - Fork 61
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
Compilation failure on OpenBSD-current #156
Comments
Thanks for reporting this @ron-at-swgy. I don't see this build error when building with clang++-16 locally on ubuntu though. Is there a specific docker container for openBSD I can use to reproduce this? Also, could you try this on main branch and let me know if you see the same error? |
I suspect the problem is related to types used on the platform. I recently had to submit a PR to a project using SWIG to generate python bindings that corrected the assumptions about type sizes.
I’ll look into getting you access to a test environment.
…--
SWGY, Inc., a Florida Corporation
https://sw.gy
On Thursday, June 20th, 2024 at 12:21 PM, Raghuveer Devulapalli ***@***.***> wrote:
Thanks for reporting this ***@***.***(https://github.com/ron-at-swgy). I don't see this build error when building with clang++-16 locally on ubuntu though. Is there a specific docker container for openBSD I can use to reproduce this? Also, could you try this on main branch and let me know if you see the same error?
—
Reply to this email directly, [view it on GitHub](#156 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/A6AZUXWLIIDDPOFAHYFYNYDZIL6QTAVCNFSM6AAAAABJQEEMG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGA4DINZSGI).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
that's my suspicion too. It might need a fix like this: x86-simd-sort/src/avx2-64bit-qsort.hpp Line 416 in 33a4a1d
|
This commit includes OpenBSD in the platform checks used to check for size_t, uint64_t, unsigned long and unsigned long long all being 64 bits in length. Addtionally, the checks for some `avx513*` flags are removed, as `avx512fp16` yield an error: "invalid cpu feature string for builtin" when compiling with clang. This commit aims to address intel#156
This commit includes OpenBSD in the platform checks used to check for size_t, uint64_t, unsigned long and unsigned long long all being 64 bits in length. Addtionally, the checks for some `avx513*` flags are removed, as `avx512fp16` yield an error: "invalid cpu feature string for builtin" when compiling with clang. This commit aims to address intel#156
This commit includes OpenBSD in the platform checks used to check for size_t, uint64_t, unsigned long and unsigned long long all being 64 bits in length. Addtionally, the checks for some `avx513*` flags are removed, as `avx512fp16` yield an error: "invalid cpu feature string for builtin" when compiling with clang. This commit aims to address intel#156
This commit includes OpenBSD in the platform checks used to check for size_t, uint64_t, unsigned long and unsigned long long all being 64 bits in length. Addtionally, the checks for some `avx513*` flags are removed, as `avx512fp16` yield an error: "invalid cpu feature string for builtin" when compiling with clang. This commit aims to address intel#156
Merged into numpy, closing this. |
Summary
When attempting to build the
v5.0
tag, I encounter compilation errors for implicit instantiation of undefined templatezmm_vector<unsigned long>
. I first encountered this issue while trying topip install numpy
fornumpy >= 2.0.0
. The trail has led me here :)Environment information
Steps to reproduce
Additional information
The complete build log can be found here.
The text was updated successfully, but these errors were encountered: