Home
last modified time | relevance | path

Searched +full:debian +full:- +full:container (Results 1 – 25 of 159) sorted by relevance

1234567

/external/mesa3d/.gitlab-ci/container/
Dgitlab-ci.yml3 .incorporate-templates-commit:
5 FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_TEMPLATES_COMMIT}"
7 .incorporate-base-tag+templates-commit:
9 …FDO_BASE_IMAGE: "${CI_REGISTRY_IMAGE}/${MESA_BASE_IMAGE}:${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT…
10 FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
12 .set-image:
14 - .incorporate-templates-commit
19 .set-image-base-tag:
21 - .set-image
22 - .incorporate-base-tag+templates-commit
[all …]
Dlava_build.sh6 # .gitlab-ci/image-tags.yml tags:
9 set -e
10 set -o xtrace
17 S3_PATH="${S3_HOST}/mesa-lava/$1/${DISTRIBUTION_TAG}/${DEBIAN_ARCH}"
18 if curl -L --retry 4 -f --retry-delay 60 -s -X HEAD \
20 echo "Remote files are up-to-date, skip rebuilding them."
28 . .gitlab-ci/container/container_pre_build.sh
30 # Install rust, which we'll be using for deqp-runner. It will be cleaned up at the end.
31 . .gitlab-ci/container/build-rust.sh
34 GCC_ARCH="aarch64-linux-gnu"
[all …]
Dcontainer_pre_build.sh3 if test -x /usr/bin/ccache; then
4 if test -f /etc/debian_version; then
6 elif test -f /etc/alpine-release; then
12 # Common setup among container builds before we get to building code.
23 ccache --show-stats
28 # lld because we're on old debian and it's buggy. mingw fails meson builds
30 find /usr/bin -name \*-ld -o -name ld | \
31 grep -v mingw | \
32 xargs -n 1 -I '{}' ln -sf '{}.gold' '{}'
34 # Make a wrapper script for ninja to always include the -j flags
[all …]
/external/wayland/
D.gitlab-ci.yml1 # This file uses the freedesktop ci-templates to build Wayland and run our
4 # ci-templates uses a multi-stage build process. First, the base container
6 # all our build dependencies. This container is aggressively cached; if a
7 # container image matching $FDO_DISTRIBUTION_TAG is found in either the
10 # quicker runtimes, however it means that any changes to the base container
14 # After the container is either rebuilt (tag mismatch) or reused (tag
15 # previously used), the build stage executes within this container.
21 # Apart from the 'variables', 'include', and 'stages' top-level anchors,
28 # by the ci-templates.
36 # For more information on ci-templates, see:
[all …]
/external/libdrm/
D.gitlab-ci.yml13 # repository's container registry, so that the image from the main
18 - project: 'freedesktop/ci-templates'
21 - '/templates/debian.yml'
22 - '/templates/freebsd.yml'
23 - '/templates/ci-fairy.yml'
30 - "Base container"
31 - "Build"
33 .ci-rules:
35 - when: on_success
39 .os-debian:
[all …]
/external/ltp/.github/workflows/
Dci.yml1 # Copyright (c) 2021-2023 Petr Vorel <pvorel@suse.cz>
11 runs-on: ubuntu-latest
14 fail-fast: false
18 - container: "debian:stable"
24 - container: "debian:stable"
27 CC: powerpc64le-linux-gnu-gcc
30 VARIANT: cross-compile
32 - container: "debian:stable"
35 CC: aarch64-linux-gnu-gcc
38 VARIANT: cross-compile
[all …]
/external/mesa3d/.gitlab-ci/test/
Dgitlab-ci.yml7 - !reference [default, before_script]
9 - rm -rf install
10 - tar -xf artifacts/install.tar
11 - section_start ldd_section "Checking ldd on driver build"
12 - LD_LIBRARY_PATH=install/lib find install/lib -name "*.so" -print -exec ldd {} \;
13 - section_end ldd_section
18 - results/
20 - !reference [.never-post-merge-rules, rules]
22 .formatting-check:
25 stage: code-validation
[all …]
/external/crosvm/docs/book/src/building_crosvm/
Dlinux.md19 git submodule update --init
30 Crosvm development best works on Debian derivatives. We provide a script to install the necessary
31 packages on Debian, Ubuntu or gLinux:
34 ./tools/install-deps
38 [Using the development container](#using-the-development-container).
40 ### Using the development container
42 We provide a Debian container with the required packages installed. With
43 [Podman](https://podman.io/getting-started/installation) or
44 [Docker](https://docs.docker.com/get-docker/) installed, it can be started with:
50 The container image is big and may take a while to download when first used. **Once started, you can
[all …]
/external/rust/crates/grpcio-sys/grpc/third_party/cares/cares/
D.cirrus.yml3 …CMAKE_FLAGS: "-DCMAKE_BUILD_TYPE=DEBUG -DCARES_STATIC=ON -DCARES_STATIC_PIC=ON -DCARES_BUILD_TESTS…
7 - name: "Debian amd64"
9 DIST: "DEBIAN"
11 SCAN_BUILD: "scan-build"
19 container:
20 image: debian:latest
21 - name: "Debian arm64"
23 DIST: "DEBIAN-ARM"
25 SCAN_BUILD: "scan-build"
32 image: debian:latest
[all …]
/external/crosvm/tools/impl/dev_container/
DDockerfile2 # Use of this source code is governed by a BSD-style license that can be
5 # Development container for crosvm.
7 # Provides all dependencies specified in install-deps with some additonal
10 # Build catapult dashboard upload tool in a builder container
17 FROM docker.io/debian:testing-slim
28 RUN mkdir -p /scratch/cargo_target \
31 # Prevent the container from writing __pycache__ files into the src.
36 RUN rm -f /etc/apt/apt.conf.d/docker-clean; echo 'Binary::apt::APT::Keep-Downloaded-Packages "true"…
38 # Add foreign architectures for cross-compilation.
39 RUN dpkg --add-architecture arm64 \
[all …]
/external/skia/infra/bots/assets/mesa_intel_driver_linux/mesa-driver-builder/
DDockerfile1 FROM debian:10.3
5 # Enabling backports gives us access to clang-6 and makes it more likely that
6 # 'apt-get build-dep' will install the correct dependencies.
13 # Hosts can install this by adding the stretch-backports debian source (see next RUN)
14 # and then performing `sudo apt-get update && sudo apt-get install libdrm2=2.4.95-1~bpo9+1`
15 RUN echo "deb-src http://deb.debian.org/debian buster main" >> /etc/apt/sources.list && \
16 echo "deb-src http://deb.debian.org/debian buster-updates main" >> /etc/apt/sources.list && \
17 apt-get update && apt-get upgrade -y && \
18 apt-get install -y wget clang-6.0 && \
19 apt-get build-dep -y mesa && \
[all …]
/external/crosvm/docs/book/src/running_crosvm/
Dcustom_kernel_rootfs.md11 to build. You can use any mainline kernel though as long as it's configured for para-virtualized
18 git clone --depth 1 -b chromeos-6.6 https://chromium.googlesource.com/chromiumos/third_party/kernel
25 CHROMEOS_KERNEL_FAMILY=termina ./chromeos/scripts/prepareconfig container-vm-x86_64
27 make -j$(nproc) bzImage
37 enough for your purposes. To get you started, a Debian rootfs can be created with [debootstrap].
41 truncate -s 20G debian.ext4
42 mkfs.ext4 debian.ext4
43 mkdir -p "${CHROOT_PATH}"
44 sudo mount debian.ext4 "${CHROOT_PATH}"
45 sudo debootstrap stable "${CHROOT_PATH}" http://deb.debian.org/debian/
[all …]
/external/wayland-protocols/freedesktop.org/
D.gitlab-ci.yml2 DEBIAN_TAG: 2019-11-21.0
4 TEST_IMAGE: "$CI_REGISTRY_IMAGE/debian/$DEBIAN_VERSION:$DEBIAN_TAG"
7 - project: 'wayland/ci-templates'
9 file: '/templates/debian.yml'
12 - containers-build
13 - test
16 extends: .debian@container-ifnot-exists
17 stage: containers-build
20 DEBIAN_DEBS: 'build-essential automake autoconf libtool pkg-config libwayland-dev'
26 - ./autogen.sh
[all …]
/external/skia/bazel/rbe/
DREADME.md9 We build our own, bare-bones, Docker image to use on RBE. We intend to use a hermetic toolchain
23 -----------------------
25 [GitHub](https://github.com/bazelbuild/bazel-toolchains/releases/tag/v5.1.1) and put that onto
29 -------------------------------
42 something like `docker run -it gcr.io/skia-public/rbe_linux:v3 /bin/bash`.
44 1) `docker pull debian:bookworm-slim` is the easiest way to see the sha256 and get the latest.
46 `Get:89 http://deb.debian.org/debian bookworm/main amd64 clang amd64 1:14.0-55.2+b1 [9976 B]`
47 5) Run `make push_linux_container` to rebuild the container and push it to GCS where it can
48 be used by our RBE workers. Note the sha256 hash of this created container
53 We chose not to use Bazel rules for this container step, as that could be difficult to bootstrap
[all …]
/external/mesa3d/.gitlab-ci/lava/
Dlava-gitlab-ci.yml2 …REGISTRY_IMAGE}/alpine/x86_64_lava_ssh_client:${ALPINE_X86_64_LAVA_SSH_TAG}--${MESA_TEMPLATES_COMM…
5 .lava-test:
10 FDO_CI_CONCURRENT: 6 # should be replaced by per-machine definitions
12 FDO_HTTP_CACHE_URI: "http://caching-proxy/cache/?uri="
13 # base system generated by the container build job, shared between many pipelines
14 BASE_SYSTEM_HOST_PREFIX: "${S3_HOST}/mesa-lava"
17 # per-job build artifacts
18 JOB_ROOTFS_OVERLAY_PATH: "${JOB_ARTIFACTS_BASE}/job-rootfs-overlay.tar.gz"
20 S3_ARTIFACT_NAME: "mesa-${ARCH}-default-debugoptimized"
25 - ./artifacts/lava/lava-submit.sh
[all …]
/external/virglrenderer/
D.gitlab-ci.yml3 MESA_TEMPLATES_COMMIT: &ci-templates-commit d5aa3941aa03c2f716595116354fb81eb8012acb
10 # at least the 'debian-testing' job in 'Build-x86_64' stage completed.
12 # Pick a pipeline on https://gitlab.freedesktop.org/mesa/mesa/-/pipelines/
18 # per-pipeline artifact storage on MinIO
20 # per-job artifact storage on MinIO
23 PIGLIT_REPLAY_REFERENCE_IMAGES_BASE: "${STORAGE_HOST}/mesa-tracie-results/${FDO_UPSTREAM_REPO}"
27 - project: 'freedesktop/ci-templates'
30 - '/templates/ci-fairy.yml'
31 - project: 'freedesktop/ci-templates'
32 ref: *ci-templates-commit
[all …]
/external/tensorflow/tensorflow/lite/tools/pip_package/
DREADME.md11 sudo apt install swig libjpeg-dev zlib1g-dev python3-dev python3-numpy
19 pip install --upgrade <wheel>
22 You can also build a wheel inside docker container using make tool. For example
23 the following command will cross-compile tflite-runtime package for python2.7
24 and python3.7 (from Debian Buster) on Raspberry Pi:
27 make BASE_IMAGE=debian:buster PYTHON=python TENSORFLOW_TARGET=rpi docker-build
28 make BASE_IMAGE=debian:buster PYTHON=python3 TENSORFLOW_TARGET=rpi docker-build
31 Another option is to cross-compile for python3.5 (from Debian Stretch) on ARM64
35 make BASE_IMAGE=debian:stretch PYTHON=python3 TENSORFLOW_TARGET=aarch64 docker-build
42 make BASE_IMAGE=ubuntu:18.04 PYTHON=python3 TENSORFLOW_TARGET=native docker-build
[all …]
Dbuild_pip_package_with_bazel.sh8 # http://www.apache.org/licenses/LICENSE-2.0
16 set -ex
19 PYTHON="${CI_BUILD_PYTHON:-python3}"
20 VERSION_SUFFIX=${VERSION_SUFFIX:-}
23 …ION = " "${TENSORFLOW_DIR}/tensorflow/tools/pip_package/setup.py" | cut -d= -f2 | sed "s/[ '-]//g")
25 export PROJECT_NAME=${WHEEL_PROJECT_NAME:-tflite_runtime}
27 TENSORFLOW_TARGET=${TENSORFLOW_TARGET:-$1}
31 export CROSSTOOL_PYTHON_INCLUDE_PATH=$(${PYTHON} -c "from sysconfig import get_paths as gp; print(g…
33 # Fix container image for cross build.
34 if [ ! -z "${CI_BUILD_HOME}" ] && [ `pwd` = "/workspace" ]; then
[all …]
/external/e2fsprogs/doc/RelNotes/
Dv1.45.1.txt7 ---------------
9 Teach the e2scrub and e2scub_all commands the -n option, which prints
18 Debugfs now prints non-printable characters using C-style hex escape
19 sequences (e.g., "\xc1" instead of M-A). The old scheme printed
26 8*blocksize (not the default), this can confuse the kernel's multi-block
38 -----
41 the lvm2 and util-linux packages are not installed, or if the commands
46 (Addresses Debian Bug: #924301)
49 in GUI's. (Addresses Debian Bug: #926112)
53 container where root does not have these capabilities. (Addresses
[all …]
/external/libbpf/ci/managers/
Ddebian.sh3 PHASES=(${@:-SETUP RUN RUN_ASAN CLEANUP})
4 DEBIAN_RELEASE="${DEBIAN_RELEASE:-testing}"
5 CONT_NAME="${CONT_NAME:-libbpf-debian-$DEBIAN_RELEASE}"
6 ENV_VARS="${ENV_VARS:-}"
7 DOCKER_RUN="${DOCKER_RUN:-docker run}"
8 REPO_ROOT="${REPO_ROOT:-$PWD}"
14 echo -e "\033[33;1m$1\033[0m"
18 echo -e "\033[31;1m$1\033[0m"
25 set -eu
33 info "Using Debian $DEBIAN_RELEASE"
[all …]
/external/curl/.github/workflows/
Dlinux-old.yml3 # SPDX-License-Identifier: curl
9 # Debian stretch is chosen as it closely matches some of the oldest major
12 # stretch has ELTS support from Feexian until 2027-06-30
13 # For ELTS info see https://www.freexian.com/lts/extended/docs/how-to-use-extended-lts/
14 # The Debian key will expire 2025-05-20, after which package signature
24 - master
25 - '*/ci'
26 paths-ignore:
27 - '**/*.md'
28 - '.azure-pipelines.yml'
[all …]
/external/sandboxed-api/.github/workflows/
Ddebian-sapi-generator-tool.yml1 name: debian-sapi-generator-tool
5 runs-on: ubuntu-latest
6 container: debian:10.13
8 - uses: actions/checkout@v3
10 - name: Cache dependencies
13 key: debian-10.13-clang16
17 - name: Install build tools
19 apt-get update
21 apt-get install -qy --no-install-recommends \
22 build-essential \
[all …]
/external/grpc-grpc/tools/docker_runners/examples/
Dgdb_in_docker.sh8 # http://www.apache.org/licenses/LICENSE-2.0
16 set -ex
23 # note that every invocation of run_tests.py with "--use_docker"
25 # This is expecially important when --compiler/--arch params are
30 # "--privileged" docker arg is required to be disable address randomization by gdb
31 # TODO: is "--security-opt=seccomp=unconfined" actually needed?
32 export DOCKER_EXTRA_ARGS="--privileged --security-opt=seccomp=unconfined"
34 # start the docker container with interactive shell
37 # Run these commands under the docker container
39 # Install gdb (or similar command for non-debian based distros)
[all …]
/external/rust/crates/grpcio-sys/grpc/tools/docker_runners/examples/
Dgdb_in_docker.sh8 # http://www.apache.org/licenses/LICENSE-2.0
16 set -ex
23 # note that every invocation of run_tests.py with "--use_docker"
25 # This is expecially important when --compiler/--arch params are
30 # "--privileged" docker arg is required to be disable address randomization by gdb
31 # TODO: is "--security-opt=seccomp=unconfined" actually needed?
32 export DOCKER_EXTRA_ARGS="--privileged --security-opt=seccomp=unconfined"
34 # start the docker container with interactive shell
37 # Run these commands under the docker container
39 # Install gdb (or similar command for non-debian based distros)
[all …]
/external/mesa3d/docs/ci/
Dindex.rst5 ---------
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),
9 as well as post-merge testing, for everything that hits ``main``
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
16 - Build testing for a number of configurations and platforms
17 - Sanity checks (``meson test``)
18 - Most drivers are also tested using several test suites, such as the
19 `Vulkan/GL/GLES conformance test suite <https://github.com/KhronosGroup/VK-GL-CTS>`__,
21 - Replay of application traces
27 tool <#running-specific-ci-jobs>`__.
[all …]

1234567