Hey Gabe, So, the docker image appears to have python3-config:
``` docker run --rm gcr.io/gem5-test/clang-version-9 python3-config ``` Returns: ``` Usage: /usr/bin/python3-config --prefix|--exec-prefix|--includes|--libs|--cflags|--ldflags|--extension-suffix|--help|--abiflags|--configdir ``` So it's in there. As far as I can tell it's been this way for a while. The Dockerfile used to build the image is `util/dockerfiles/ubuntu-18.04_clang-version/Dockerfile`. I'm confused by this, I don't think anything should "leak" into the image in this way. Could you link me to an example of this issue happening? -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Feb 10, 2021 at 10:21 PM Gabe Black <gabe.bl...@gmail.com> wrote: > Hi folks. I was trying to debug a problem in one of my scons cleanups > which was failing on kokoro when trying to build under clang. I think I > fixed it, but after doing so it started to fail because it didn't like the > version of python it was finding, and sure enough that image has > python-config and python2.7-config installed on it, but no python3-config > even though it has python 3. > > Does anybody know what's going on here? My best guess is that values from > a previous build using a docker image that does have python3-config are > leaking through and making the subsequent build with this image work, even > though it doesn't work when done first. > > Where should I/we look to fix this image so it has python3-config on it? > > Gabe >
_______________________________________________ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
