Closed Ivan-Velickovic closed 5 months ago
Doesn't happen on a fresh checkout of sel4bench, must be some cache from builds outside of Docker or something leaking in? I don't know.
Doesn't happen on a fresh checkout of sel4bench, must be some cache from builds outside of Docker or something leaking in? I don't know.
That would make sense (left-overs in the build from work outside the container)
sel4bench as such builds regularly in the docker container (this is what CI uses)
It was a different build directory, which I would expect to work. Anyways, I guess this kind of thing is outside of the scope of Docker.
I was building sel4bench and was getting compile errors due to extra GCC warnings, so I thought I'd use the compiler in the Docker container just to check that it works in there since an older compiler is used.
I did:
and got the following output: