Closed shantanoo-desai closed 3 years ago
Hi @shantanoo-desai , it's been quite a while since I used my own docker image and I know that there has been changes to the packages needed to build OP-TEE. So, it's probably just the list of packages that needs to be updated in the Dockerfile. I think we can close the issue here, since this has nothing to do with build.git
. That git works with the official tree's, my docker images are the culprit here.
Sounds good. For posterity, would you suggest I open the issue in the docker repository since it still is an issue which I am unable to troubleshoot? @jbech-linaro
Sounds good. For posterity, would you suggest I open the issue in the docker repository since it still is an issue which I am unable to troubleshoot? @jbech-linaro
Sure.
@shantanoo-desai FYI:
$ dpkg -S `which iasl`
acpica-tools: /usr/bin/iasl
Try apt install acpica-tools
, that should help.
And, note that the Docker image we use for CI (here: https://github.com/OP-TEE/optee_os/blob/3.15.0/.azure-pipelines.yml#L229) has this acpica-tools
installed: https://github.com/jforissier/docker_optee_os_ci/blob/0b0a1cf/Dockerfile#L42 (this Dockerfile is in the qemuv8_check
branch). You may want to check the package list, it should always be up to date. Note the Docker image itself is quite big though because it contains the whole OP-TEE tree pre-built to speed up CI, so it might not be a good idea to use this image for your purposes. In any case the package list should be helpful.
Host Information
x86_64
MachineDocker version 20.10.9, build c2ea9bc90b
Reproduction Steps
I am using @jbech-linaro's docker-optee Image which provides me the base image for trying out OP-TEE.
I did the following from within the container: (current PWD is
build
)make -j4 run all
which does produce any errorsmake run
causes the following erroriasl not found
Error Logs
Additional Information
it turns out when executing the following:
which in turn mentions there is no
out/bin
directory.I create the following directory
out/bin
in the root directory and it does run for a bit, which opens Two xterms on my host machine however it causes the following error:What could be the potential problem here?