TryThisOneMyFriend commented on issue #12014: URL: https://github.com/apache/trafficserver/issues/12014#issuecomment-2660849660
> A few thoughts: > > We maintain Docker CI images with both of these installed in them: ci.trafficserver.apache.org/ats/fedora:41 . I'm not sure whether that fits your workflow, but that may be helpful. > > For cmake arguments, here are the Preset values for the boringssl build our Rocky CI uses (you can ignore the `opentelemetry_ROOT` part): > > [trafficserver/CMakePresets.json](https://github.com/apache/trafficserver/blob/54b42b11a54d80a98190584a3e3518625d7a0f38/CMakePresets.json#L150-L154) > > Lines 150 to 154 in [54b42b1](/apache/trafficserver/commit/54b42b11a54d80a98190584a3e3518625d7a0f38) > "OPENSSL_ROOT_DIR": "/opt/h3-tools-boringssl/boringssl", > "quiche_ROOT": "/opt/h3-tools-boringssl/quiche", > "CMAKE_INSTALL_PREFIX": "/tmp/ats-quiche", > "opentelemetry_ROOT": "/opt", > "ENABLE_QUICHE": "ON" > > That assumes boringssl was installed like so: > > BASE=/opt/h3-tools-boringssl tools/build_boringssl_h3_tools.sh So i tried to change it in the debian ci since i'm using bookworm. I executed it and got the same error. I tried to force it, as described by the tutorial, with the following command: `cmake -DOPENSSL_ROOT_DIR=/opt/h3-tools-boringssl/boringssl -DOPENSSL_INCLUDE_DIR=/opt/h3-tools-boringssl/boringssl/include -Dquiche_ROOT=/opt/h3-tools-boringssl/quiche -DENABLE_QUICHE=TRUE -DCMAKE_INSTALL_PREFIX=/opt/ats -B build -G Ninja` Neither worked. Anyway, I'm rethinking installing it anyway. Apparently the quic protocol available to us in test is just not as good as the http2. so I will be putting this installation on halt in my system for now. I won't be closing this topic though in case there is anyone with the same problem wich wants to add something up. Thanks to everyone for your help. -- 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]
