bneradt opened a new issue, #10232:
URL: https://github.com/apache/trafficserver/issues/10232

   We have agreed to support cmake 3.20 for our cmake builds. I'm getting ready 
to create a CI job to build with cmake 3.20 and I tested a build with this in 
rockylinux:8. I observed this cmake failure:
   
   https://ci.trafficserver.apache.org/job/Github_Builds/job/rocky/2979/console
   
   ```
   + cmake --install cmake-build-quiche
   -- Install configuration: "Debug"
   -- Installing: /tmp/ats_quiche/lib64/libfastlz.so
   ...
   -- Set runtime path of 
"/tmp/ats_quiche/libexec/trafficserver/healthchecks.so" to "/tmp/ats_quiche/lib"
   -- Installing config: /tmp/ats_quiche/etc/trafficserver/records.yaml
   CMake Error at cmake/install_configs.cmake:33 (file):
     file does not recognize sub-command COPY_FILE
   Call Stack (most recent call first):
     cmake-build-quiche/configs/cmake_install.cmake:54 (include)
     cmake-build-quiche/cmake_install.cmake:132 (include)
   ```
   
   In the meantime, I'll revert PR CI Rocky jobs to use automake.
   
   ## Reproduction steps:
   
   ```sh
   docker pull ci.trafficserver.apache.org/ats/rockylinux:8
   docker run --rm -it ci.trafficserver.apache.org/ats/rockylinux:8 /bin/bash
   
   # Now, from inside docker.
   source /opt/rh/gcc-toolset-11/enable
   
   cd /var/tmp
   git clone https://github.com/apache/trafficserver.git
   cd trafficserver
   
   cmake -B cmake-build-quiche -DCMAKE_COMPILE_WARNING_AS_ERROR=ON 
-DENABLE_QUICHE=ON -DCMAKE_BUILD_TYPE=Debug -DBUILD_EXPERIMENTAL_PLUGINS=ON 
-Dquiche_ROOT=/opt/quiche -DOPENSSL_ROOT_DIR=/opt/boringssl 
-DCMAKE_INSTALL_PREFIX=/tmp/ats_quiche
   cmake --build cmake-build-quiche -j4 -v
   cmake --install cmake-build-quiche
   
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to