Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*: add cross-build, CI job, update to libseccomp 2.5.2 #3197

Merged
merged 4 commits into from
Sep 22, 2021

Commits on Sep 20, 2021

  1. Makefile: fixes for seccompagent

    1. The seccompagent target it built in the same way as others in contrib,
       so there is no need to have a separate rule.
    
    2. Mark seccompagent as phony, because it is (it rarely happens, but I
       actually just had an issue because this was absent).
    
    3. Add seccompagent binary to clean target.
    
    Fixes: e21a9ee
    
    Signed-off-by: Kir Kolyshkin <[email protected]>
    kolyshkin committed Sep 20, 2021
    Configuration menu
    Copy the full SHA
    d2b6899 View commit details
    Browse the repository at this point in the history
  2. Makefile: only build runc for static target

    There is no need to have a static version of recvtty and/or sd-helper
    binary.
    
    This speeds up script/release.sh a bit.
    
    Signed-off-by: Kir Kolyshkin <[email protected]>
    kolyshkin committed Sep 20, 2021
    Configuration menu
    Copy the full SHA
    23d79aa View commit details
    Browse the repository at this point in the history
  3. make release: add cross-build

    This implements cross-build for "make release", moving the build into a
    container. This way we can support arm, arm64, ppc, and whatnot.
    
    * script/seccomp.sh: separate out of script/release.sh, amend to support
      cross-compile and save needed environment variables to a file.
    
    * Dockerfile: add installing libseccomp from source, as this is needed
      for release builds.
    
    * script/release.sh: amend to support more architectures in addition to
      the native build. Additional arches can be added by specifying
      "-a <arch>" argument (can be specified multiple times), or
      "make RELEASE_ARGS="-a arm64" release" if called via make.
      All supported architectures can be enabled via "make releaseall".
    
    * Makefile: move "release" target to "localrelease", add "release" and
      "releaseall" targets to build via the Dockerfile. This is done because
      most distros (including Fedora and openSUSE) lack cross-glibc, which is
      needed to cross-compile libseccomp.
    
    * Makefile: remove 'cross' and 'localcross' targets, as this is now done
      by the release script.
    
    * .github/workflows/validate.yum: amend the release CI job to cross-build
      for supported architectures, remove cross job.
    
    Signed-off-by: Kir Kolyshkin <[email protected]>
    kolyshkin committed Sep 20, 2021
    Configuration menu
    Copy the full SHA
    f30244e View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    3c8db63 View commit details
    Browse the repository at this point in the history