Skip to content

Latest commit

 

History

History
56 lines (44 loc) · 2.07 KB

README.docker.md

File metadata and controls

56 lines (44 loc) · 2.07 KB

Overview

Runs compilertron in a docker container

Prereqs

  • Docker
  • If you're running Docker in a VM, ensure you allocate 8-16GB RAM and 10 cores
  • Otherwise adjust the make -j## stanzas in the build scripts

Setup

Usage

docker build .

Stages are listed in the Dockerfile in the FROM entries:

FROM  sgug_binutils as sgug_gcc

In this example, the stage is 'sgug_gcc'.

You can specify a stage to build, which will skip the prior stages (if they are unchanged), saving time.

docker build --target sgug_gcc .

Debugging

Given this error:

make[3]: Leaving directory '/root/rpmbuild/BUILD/gcc-9.2.0-20190812/libcc1'
make[2]: Leaving directory '/root/rpmbuild/BUILD/gcc-9.2.0-20190812/libcc1'
/bin/bash: line 3: cd: mips-sgi-irix6.5/libssp: No such file or directory
make[1]: *** [Makefile:11439: install-target-libssp] Error 1
make[1]: Leaving directory '/root/rpmbuild/BUILD/gcc-9.2.0-20190812'
make: *** [Makefile:2315: install] Error 2
Removing intermediate container a1125d4886bc
 ---> 560e87405a9c
 Successfully built 560e87405a9c

Docker has created a container with id 560e87405a9c .

You may run it interactively:

docker run -it 560e87405a9c bash

Note that changes must be made in the Dockerfile and a new container must be built for those changes to persist. Any interactions within a running container are ephemeral.