1ae2786c7c
It is good practice to use an explicit registry for referencing the base image. This is because some distros will inject their own registries into the search path. For example registry.fedoraproject.org comes ahead of docker.io. Using an explicit registry avoids wasting time querying multiple registries for images that they won't have. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20210623142245.307776-5-berrange@redhat.com> Message-Id: <20210709143005.1554-13-alex.bennee@linaro.org>
30 lines
1 KiB
Docker
30 lines
1 KiB
Docker
#
|
|
# Docker cross-compiler target
|
|
#
|
|
# This docker target builds on the debian stretch base image,
|
|
# using a prebuilt toolchains for Xtensa cores from:
|
|
# https://github.com/foss-xtensa/toolchain/releases
|
|
#
|
|
FROM docker.io/library/debian:stretch-slim
|
|
|
|
RUN apt-get update && \
|
|
DEBIAN_FRONTEND=noninteractive apt install -yy eatmydata && \
|
|
DEBIAN_FRONTEND=noninteractive eatmydata \
|
|
apt-get install -y --no-install-recommends \
|
|
build-essential \
|
|
ca-certificates \
|
|
curl \
|
|
gettext \
|
|
git \
|
|
python3-minimal
|
|
|
|
ENV CPU_LIST dc232b dc233c de233_fpu dsp3400
|
|
ENV TOOLCHAIN_RELEASE 2020.07
|
|
|
|
RUN for cpu in $CPU_LIST; do \
|
|
curl -#SL http://github.com/foss-xtensa/toolchain/releases/download/$TOOLCHAIN_RELEASE/x86_64-$TOOLCHAIN_RELEASE-xtensa-$cpu-elf.tar.gz \
|
|
| tar -xzC /opt; \
|
|
done
|
|
|
|
ENV PATH $PATH:/opt/$TOOLCHAIN_RELEASE/xtensa-dc232b-elf/bin:/opt/$TOOLCHAIN_RELEASE/xtensa-dc233c-elf/bin:/opt/$TOOLCHAIN_RELEASE/xtensa-de233_fpu-elf/bin:/opt/$TOOLCHAIN_RELEASE/xtensa-dsp3400-elf/bin
|