From dc246cf81a87b965a8785741ff460529be634ce7 Mon Sep 17 00:00:00 2001 From: ArchanaShinde1 Date: Wed, 28 Aug 2024 05:33:17 +0000 Subject: [PATCH 1/2] Update 195-cpd README --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index c9ff03ab..508d0450 100644 --- a/README.md +++ b/README.md @@ -76,6 +76,7 @@ pip install -e . | 1.7.10 | 12.0.2 | | 1.8.1 | 12.0.2 | | 1.9.4 | 12.0.3 | +| 1.9.5-cpd | 12.0.3 | ### Building a Collection of Packages @@ -148,6 +149,11 @@ One can build Open-CE packages with ffmpeg in two ways: - Provide `--fips` option to the `open-ce build env` command. This will use the `openssl-env.yaml`, which includes `ffmpeg` by default. +### Build instructions for ppc (p9 and p10) +Setuptools v72.1.0 (The default Conda channel does not have the CVE patch version available) can be build on ppc p9 and p10 +1. Set `export CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0` and then build common-deps.yaml +2. `unset CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY` and then build opence-env.yaml. + ### Building within a container Passing the `--container_build` argument to the `open-ce build env` command will create a container image and perform the actual build inside of a container based on that image. This will provide a "clean" environment for the builds and make builds more system independent. It is recommended to build with this option as opposed to running on a bare metal machine. For more information on the `--container_build` option, please see [`doc/README.open_ce_build.md`](doc/README.open_ce_build.md#open-ce-build-env-sub-command). From a432f2e6532668ca2ba74e2a35b133cfbaaeba36 Mon Sep 17 00:00:00 2001 From: ArchanaShinde1 Date: Wed, 28 Aug 2024 07:23:07 +0000 Subject: [PATCH 2/2] Update README --- README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 508d0450..b786c502 100644 --- a/README.md +++ b/README.md @@ -119,6 +119,13 @@ open-ce build env --python_versions 3.8,3.9,3.10 --build_types cuda opence-env Note that having _conda-forge_ in your channel list may sometime cause conflicts or unexpected errors due to dependencies' versions mismatch. So, it is recommended to avoid mixing the channels during the build as well as at runtime. +### Note: +Ensure CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0 is set before building setuptools v72.1.0 +The steps to build setuptools with this environment variable and before other packages are: +1. Set export CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0 +2. Build common-deps.yaml +3. unset CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY +4. Build opence-env.yaml. ### Power10 MMA Optimization #### Building Packages @@ -149,11 +156,6 @@ One can build Open-CE packages with ffmpeg in two ways: - Provide `--fips` option to the `open-ce build env` command. This will use the `openssl-env.yaml`, which includes `ffmpeg` by default. -### Build instructions for ppc (p9 and p10) -Setuptools v72.1.0 (The default Conda channel does not have the CVE patch version available) can be build on ppc p9 and p10 -1. Set `export CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY=0` and then build common-deps.yaml -2. `unset CONDA_ADD_PIP_AS_PYTHON_DEPENDENCY` and then build opence-env.yaml. - ### Building within a container Passing the `--container_build` argument to the `open-ce build env` command will create a container image and perform the actual build inside of a container based on that image. This will provide a "clean" environment for the builds and make builds more system independent. It is recommended to build with this option as opposed to running on a bare metal machine. For more information on the `--container_build` option, please see [`doc/README.open_ce_build.md`](doc/README.open_ce_build.md#open-ce-build-env-sub-command).