-
Notifications
You must be signed in to change notification settings - Fork 30
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
Use Python 3.9 [in public CI] #599
Conversation
PokhodenkoSA
commented
Sep 28, 2021
•
edited
Loading
edited
- Update CI
- Update conda recipe
- Use intel channel
I had to disable intel channel for building because of CMake compiler check fail. |
Is it perhaps better to restrict the version of cmake than to remove the intel channel. We need to be sure we are picking correct run time bits. |
Thank for the idea. I will check that the problem is really in cmake version. |
This reverts commit d1ffeb6.
Problem is not related to CMake. |
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.
LGTM!
@AndresGuzman-Ballen Why isn't the compiler package carrying the run-time? If run-time is not present, how can it be a viable compiler package? |
@oleksandr-pavlyk Sergey already answered why this is appearing in Python 3.9 and not Python 3.8. What I imagine is happening is that dpctl is expecting the runtimes to be found in the host prefix but since {{ compiler('dpcpp') }} is a build dependency, it is being installed in the build prefix instead |
@AndresGuzman-Ballen Per @PokhodenkoSA's explanation, it is the compiler that requires dpctl Python extensions should not be built using dpcpp/clang at present, only the backend library. I am trying to build the recipe locally. |
The build environment is indeed viable, as once I activate it, I am able to build a simple C++ program that uses SYCL. This means that build environment already contains all the components in DPC++ launched by cmake does not see those components, because conda build isolates I was able to build Python 3.9 package using diff --git a/conda-recipe/build.sh b/conda-recipe/build.sh
index 37ae591..f2df115 100755
--- a/conda-recipe/build.sh
+++ b/conda-recipe/build.sh
@@ -3,10 +3,11 @@
# Workaround to Klocwork overwriting LD_LIBRARY_PATH that was modified
# by DPC++ compiler conda packages. Will need to be added to DPC++ compiler
# activation scripts.
-export LDFLAGS="$LDFLAGS -Wl,-rpath,$CONDA_PREFIX/lib"
+export LDFLAGS="$LDFLAGS -Wl,-rpath,$PREFIX/lib"
${PYTHON} setup.py clean --all
-INSTALL_CMD="install --sycl-compiler-prefix=$CONDA_PREFIX"
+INSTALL_CMD="install --sycl-compiler-prefix=$BUILD_PREFIX"
+export LD_LIBRARY_PATH=$BUILD_PREFIX/lib:${LD_LIBRARY_PATH}
if [ -n "${WHEELS_OUTPUT_FOLDER}" ]; then
# Install packages and assemble wheel package from built bits
diff --git a/conda-recipe/meta.yaml b/conda-recipe/meta.yaml
index 77c7814..ce4da0b 100644
--- a/conda-recipe/meta.yaml
+++ b/conda-recipe/meta.yaml
@@ -22,7 +22,7 @@ requirements:
- python
- make # [unix]
- ninja # [win]
- - numpy >=1.17 # [win or osx or py==38]
+ - numpy >=1.17 # [win or osx or py>=38]
- numpy 1.17 # [linux and py==37]
- wheel
run: I used standard |
I have applied Sasha's changes. LGTM. |
I have made job "Generate coverage data / Generate coverage and push to Coveralls.io" as not required because it fails on master too. |
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.
LGTM