OK, I am sorry it was not that easy.
No problem. I appreciate the help. If we figure this out, maybe we'll
learn something to make it easier :)
RUN tar -xf bigloo4.3f.tar.gz && mv bigloo4.3f bigloo
Why do you need the renaming?
This is not a normal build step (without Docker).
It's not necessary; it's just for our convenience maintaining the
container. Since we'll be keeping up with new versions of Bigloo, we can
make less changes to the Dockerfile if the directory name can stay the
same for all versions.
WORKDIR /bigloo
Is the / ok?
Yes - the Docker container has its own isolated file system and
processes, so it's simpler to do everything as root. You can make other
users inside the container, and maybe we should, but it's not that
important since users inside the container cannot access anything
outside the container.
RUN ./configure
RUN make
Please pipe the output of these commands into files and post them.
Sorry - I should have done that right away. Here is the entire Docker
build log (output of running "docker build -t bigloo ." in the directory
with the Dockerfile): <https://misc.lassi.io/2019/bigloo-docker-build.log>.
