Hello, community! I happen to do some work on a Pants-built python app from a colleague that recently left the company and I have an issue, which I prefer to address here instead of stackoverflow. So, the issue is that we need to run this pants app on RHEL 9, 8 and 7 and we build it on CentOS 7 (which works on rhel7 / 8 as expected), but on RHEL 9, I get a glibc error : "return code=1, stdout=, stderr=awk: /tmp/_MEIu4qVxf/libm.so.6: version `GLIBC_2.29' not found (required by awk)". I've also tried to build it on rhel 8, but throws the same error as above. Also attaching an output of glibc backwards compat. Building the pants bin directly on RHEL 9 works correctly. Do you have any idea how to make it run from rhel 7 to all the upcoming distros? Thanks alot!

I'm focusing on this: "...`GLIBC_2.29' not found (required by awk)" Read literally, that says `awk`requires glibc 2.29 and

awk

is a native program, not Python at all. Does the Pants Python app (I assume you mean a PEX produced by Pants and not

./pants

itself) contain a copy of

awk

or does the it try to invoke the system

awk

in a subprocess? PEXes are just zipfiles; so you can use

zipinfo <your PEX python app>

or unzip it and inspect that way.

Thanks for the answer, pants version is 2.6.1

Ok, And was I right in assuming by Pants Python app you meant a Python application packaged by Pants; in other words a

python_binary

(or

pex_binary

) app produced by running

./pants package ...

resulting in an app file emitted under

dist/...

?

yes, that is correct

Aha, Pants does not produce tarballs. Your repo must have a custom Pants plugin that does this. What is the Pants command line you run to generate this tarball?

cmd1='rm -rf dist && ./pants --version && ./pants filter --filter-target-type=python_distribution :: | xargs ./pants package && ./pants filter --filter-target-type=pex_binary :: | xargs -i -d ":" -n 2 '${RUNNING_DIR_RELATIVE}'/build_installer_binary.sh' cmd2='rm -rf dist && ./pants --version && ./pants filter --filter-target-type=python_distribution :: | xargs ./pants package && ./pants --changed-since='${BRANCH}' --changed-dependees=transitive filter --filter-target-type=pex_binary --address-regex="^(.(?!(.py:)))*$" | xargs -i -d ":" -n 2 '${RUNNING_DIR_RELATIVE}'/build_installer_binary.sh' cmd=$(setCmd "${cmd1}" "${cmd2}") bash -c "${cmd}"

And, while I have you, if you can share your pants.toml (or pants.ini), that would help determine if you do, in fact, have custom plugins. In modern Pants this is found in the GLOBAL section

only pyinstaller and staticx commands

Ok, well then no Pants is involved. ALl the Pants commands you listed above just produce Pants metadata.

right, I see the libm added here

So pyinstaller is not Pants. The Pantsbuild team does not maintain that project.

I wonder what's the purpose of Pants here

No clue. I agree it seems very very strange.

Looks like you're using Pants to query dependency metadata and do change analysis, but not actually run any processes!

found the solution -> https://pyinstaller.org/en/stable/runtime-information.html#ld-library-path-libpath-considerations

Ah, excellent. You're welcome.