-
Notifications
You must be signed in to change notification settings - Fork 5
env/: Implement Docker environment #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
20b9aae
to
08ef3f7
Compare
4b6173f
to
9093c05
Compare
Unfortunately it seems there is an inconsistency with the First of all, the prerequisite versions of which is a little weird since when following scenarios from Another thing is, that specific version ( As you can see in these logs, having This issue stopped happening when we switched over to Therefore for now we will stick with |
3798842
to
64796cd
Compare
Thank you for this! |
@DavidMCerdeira Hi, The only thing I can think of at the top of my head that could be causing issues is maybe you
|
@DavidMCerdeira Hi, have you tried building again? Can you try following the exact commands posted above and show your output? |
Signed-off-by: Eduard Kaverinskyi <[email protected]> Co-authored-by: Tymoteusz Burak <[email protected]>
3ab5959
to
6c30b9f
Compare
To be able to configure the end OS with `make menuconfig`
Signed-off-by: Daniil Klimuk <[email protected]>
4edb734
to
6f86d8e
Compare
We should be setting the environment variables in Dockerfile
6f86d8e
to
cefe380
Compare
I've merged PR's from our side and cleaned the PR contents a little. The instructions should be now straightforward to follow. I also fixed problems that we had with compiling Trusted Applications by adding the libteec2 from Debian trixie (testing) branch. Here are the logs from the whole build process from inside the container (logged with the |
This PR starts to get a little messy. I'm not sure how to proceed with that.
In the logs you can see that the TA's compiled and work in the end image but some time later when building i got similiar bugs as to before with the linker. Not sure why that is. For sure before merging we need to ensure that the build.sh produces at least some reproducable output. |
I retested and was able to build the docker container.
I think I have some idea of what's causing this. |
I got a similar issue when using the same bash session to compile for both RISC-V and Arm |
I am a bit out of context here. Do you mean the |
This implements WIP Docker environment with dependencies.
Currently we are able to install correct versions of all the dependencies. The toolchain installed is
aarch64-none-elf-gcc
.Right now build fails because it tries to use
aarch64-linux-gnu-gcc
, whileaarch64-none-elf-gcc
is the toolchain listed in the requirements.