Sorry I hadn't gotten back to you about this. Your explanation made sense (stale docker), but I wanted to try it out before replying to make sure that was it. I have now, and that command (less the http:// prefix which it didn't like) said it downloaded an update. After that, "which python3-config" had output. Thanks!
Gabe On Sun, Feb 14, 2021 at 12:53 AM Bobby Bruce <bbr...@ucdavis.edu> wrote: > I can't recreate the "clang-version-9 docker image without python3-config" > bug on my end . I also had a little check of Kokoro and found the image > there to be fine: > https://gem5-review.googlesource.com/c/public/gem5/+/41373. > python3-config appears to exist on the image inside Kokoro. > > I _think_ what you have is an out-of-date image on whatever system you're > running on. I don't know under what circumstances docker will pull the > latest version of an image, but you can do so manually with `docker pull > http://gcr.io/gem5-test/clang-version-9` > <http://gcr.io/gem5-test/clang-version-9>. Can you do that and try again? > I think this will solve your problem. > > -- > Dr. Bobby R. Bruce > Room 2235, > Kemper Hall, UC Davis > Davis, > CA, 95616 > > web: https://www.bobbybruce.net > > > On Fri, Feb 12, 2021 at 5:35 PM Gabe Black <gabe.bl...@gmail.com> wrote: > >> Hi Bobby, that's not the docker I'm using. The one I'm using is >> gcr.io/gem5-test/clang-version-9 which is the one run as part of the >> presubmit tests (see original email). There may have been drift between >> that and the compiler tests? When I run that docker interactively >> (otherwise the same command as in the presubmit script) I get the following: >> >> $ docker run -i -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) --rm " >> gcr.io/gem5-test/clang-version-9" >> which python3-config >> python3-config >> /bin/bash: line 2: python3-config: command not found >> >> There's no command prompt so what is the output of what may not be clear. >> I typed the "which" line which produced no output (nothing found). Then I >> typed python3-config which returned the error message on the last line. >> >> The "leak" I'm referring to would be if the original build of gem5 (for >> the regressions) figured out, for instance, where to get the python library >> from, etc. scons will cache these values between builds to speed up build >> time, and may not attempt to redetermine those values which it would no >> longer be able to do once python3-config goes away in the second run. I >> think it does try to figure out when those values are stale and rerun >> config checks, but in my experience it's not 100% accurate and may not >> retry when it really should. That could be hiding the error in this case. >> >> Gabe >> >> On Fri, Feb 12, 2021 at 10:37 AM Bobby Bruce <bbr...@ucdavis.edu> wrote: >> >>> 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
