Closed zach-morris closed 2 months ago
pkg-config
is available on the cflinuxfs4
stack:
→ docker run -it --rm cloudfoundry/cflinuxfs4 pkg-config --version
0.29.2
So it sounds like we're missing some config. Can you try adding some environment variables to staging to validate what the buildpack could add?
I'm going to close this out as there's been no response in over a year.
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
? cf cli version 7.5.0+0ad1d6398.2022-06-04 Running on: VMware TAS for VMs v2.13.16What version of the buildpack you are using? v1.8.11 (python_buildpack_latest)
If you were attempting to accomplish a task, what was it you were attempting to do? Push app / build python application using the noted buildpack with a requirements.txt file containing (no version limitation):
Manifest.yml:
requirements.txt:
What did you expect to happen? The app succeeds to build using the latest python buildpack
What was the actual behavior? The app fails to build with error:
I'll note that the build succeeds if i update the requirements.txt file to:
After further investigation, i see that the latest version of mysqlclient (2.2.0 released June 21,2023), has been updated and now uses pkg-config instead of mysql_config (ref https://github.com/PyMySQL/mysqlclient/pull/586), which is the root cause of the failure. I assume the python_buildpack would have to include pkg-config to allow this to succeed with the newest versions of mysqlclient, or define the environment variables for the buildpack as suggested here: https://github.com/PyMySQL/mysqlclient#customize-build-posix
Please confirm where necessary: