workingjubilee commented on issue #5719:
URL: https://github.com/apache/arrow-rs/issues/5719#issuecomment-2107331662

   > Seems to be an issue with the `apache/arrow-dev:amd64-conda-integration` 
Docker image, specifically with conda?
   > 
   > Relevant discussions:
   > 
   >     * [g++ cannot find sys/auxv.h on ubuntu 18.04 
conda-forge/ctng-compiler-activation-feedstock#88](https://github.com/conda-forge/ctng-compiler-activation-feedstock/issues/88)
   > 
   >     * [Missing header auxv.h 
conda-forge/conda-forge.github.io#1625](https://github.com/conda-forge/conda-forge.github.io/issues/1625)
   > 
   > 
   > Apparently need `sysroot_linux-64>=2.16` but when I check manually in the 
Docker image:
   > 
   > ```shell
   > arrow-rs$ docker run --rm -it --entrypoint bash 
apache/arrow-dev:amd64-conda-integration
   > root@9c44f644db4a:/# conda list sysroot_linux-64
   > # packages in environment at /opt/conda/envs/arrow:
   > #
   > # Name                    Version                   Build  Channel
   > sysroot_linux-64          2.12                he073ed8_17    conda-forge
   > root@9c44f644db4a:/# echo '#include <sys/auxv.h>' | g++ -c -x c++ -
   > <stdin>:1:10: fatal error: sys/auxv.h: No such file or directory
   > compilation terminated.
   > root@9c44f644db4a:/#
   > ```
   > 
   > Not too familiar with this stuff but I guess issue would lie upstream in 
arrow repo 🤔
   
   @Jefffrey I'm sorry, is sysroot_linux-64 with a version of 2.12 not in fact 
less than and not greater than 2.16?
   
   This issue should be reopened, as the problem was not actually fixed. The 
actual minimum is 2.17 and has been for a long time so there will be no 
upstream fix for this: 
https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html


-- 
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