Bump patchelf from 0.13.1 -> 0.18.0

[zanieb]

[bhilton]

FYI, on a similar project I found that moving to patchelf 0.18.0 broke my tools due to this open issue: https://github.com/NixOS/patchelf/issues/492. You may want to use 0.17.2 until the issue with older versions of glibc has been resolved.

[zanieb]

Thanks!

[zanieb]

I opened a second pull request — https://github.com/indygreg/python-build-standalone/pull/366

I'll close this one if it fails.

[zanieb]

Failing with

patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with -std=c++17...
patchelf> no
patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with +std=c++17...
patchelf> no
patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with -h std=c++17...
patchelf> no
patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with -std=c++1z...
patchelf> no
patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with +std=c++1z...
patchelf> no
patchelf> checking whether /usr/bin/x86_64-linux-gnu-g++ supports C++17 features with -h std=c++1z...
patchelf> no
patchelf> configure: error: *** A compiler with support for C++17 language features is required.

[indygreg]

I guess we build patchelf with the old GCC toolchain in the container image. We should be able to build against our modern LLVM as a workaround. But if there are issues with modern patchelf, we may need to hold off.