psiroky opened a new issue, #812:
URL: https://github.com/apache/maven-mvnd/issues/812

   As part of https://github.com/apache/maven-mvnd/pull/801 I upgraded the 
ubuntu build image from `ubuntu:18.04 to ubuntu:22.04`, mainly because GitHub 
is removing the support for that old ubuntu image. With that I also 
inadvertently bumped the minimum requirement for the Glibc the native binary 
needs, which now seems to be `2.32`.
   
   Then I noticed the patch for Graal in the build script: 
   ```
   - name: 'Patch Graal libs for only requiring glibc 2.12'
     shell: bash
     run: |
             if [[ $OS == linux ]] && [[ $GRAALVM_HOME ]] && [[ -d 
"$GRAALVM_HOME/lib/static/linux-amd64/glibc" ]]; then
               mkdir -p client/target/graalvm-libs-for-glibc-2.12
               echo "memcpy memcpy@GLIBC_2.2.5" >client/target/glibc.redef
               echo "posix_spawn posix_spawn@GLIBC_2.2.5" 
>>client/target/glibc.redef
               find "$GRAALVM_HOME/lib/static/linux-amd64/glibc" -name '*.a' | 
while IFS= read -r input; do
                 output="client/target/graalvm-libs-for-glibc-2.12/$(basename 
-- "$input")"
                 objcopy --redefine-syms=client/target/glibc.redef -- "$input" 
"$output" 2>/dev/null
               done
               find /usr/lib -name libz.a | xargs -r -I {} objcopy 
--redefine-syms=client/target/glibc.redef {} 
client/target/graalvm-libs-for-glibc-2.12/libz.a
             fi
   ```
   The patch suggests that `mvnd` should support glibc 2.12, which is no longer 
the case.
   
   This the output I get when running on ubuntu 18.04 and ubuntu 20.04, with 
latest binaries from master:
   ```
   /tmp/mvnd-test ❯ podman run -it -v .:/mvnd ubuntu:18.04 bash                 
                                                                                
                                                                                
                                                                         
   root@542c2dc5feba:/# 
./mvnd/maven-1.0.0-m5-SNAPSHOT-mvnd-m39-linux-amd64/bin/mvnd --version
   ./mvnd/maven-1.0.0-m5-SNAPSHOT-mvnd-m39-linux-amd64/bin/mvnd: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
./mvnd/maven-1.0.0-m5-SNAPSHOT-mvnd-m39-linux-amd64/bin/mvnd)
   ./mvnd/maven-1.0.0-m5-SNAPSHOT-mvnd-m39-linux-amd64/bin/mvnd: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
./mvnd/maven-1.0.0-m5-SNAPSHOT-mvnd-m39-linux-amd64/bin/mvnd)
   ```
   
   Now, I am not sure about the intended supportability for different glibc 
versions. Ubuntu 18.04 is already pretty old and according to 
https://wiki.ubuntu.com/Releases, the end of standard support is like a month 
away. So maybe that one could be dropped? But then it seems like `mvnd` should 
still support at least ubuntu 20.04, which will be supported for another two 
years.
   
   


-- 
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: issues-unsubscr...@maven.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to