public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] gitlab-ci: add build for MIPS
Date: Tue, 18 Jun 2019 12:27:03 +0100	[thread overview]
Message-ID: <0085aaa7-1c75-524b-c74c-955f862cc931@collabora.com> (raw)
In-Reply-To: <20190614103356.m7s2gx66pnvthaw7@ahiler-desk1.fi.intel.com>

On 14/06/2019 11:33, Arkadiusz Hiler wrote:
> On Thu, Jun 13, 2019 at 03:01:06PM +0100, Guillaume Tucker wrote:
>> Add Docker image and Gitlab CI steps to run builds for the MIPS
>> architecture using Debian Stretch with backports.
>>
>> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
>> ---
>>  .gitlab-ci.yml         | 28 ++++++++++++++++++++++++++++
>>  Dockerfile.debian-mips | 39 +++++++++++++++++++++++++++++++++++++++
>>  meson-cross-mips.txt   | 12 ++++++++++++
>>  3 files changed, 79 insertions(+)
>>  create mode 100644 Dockerfile.debian-mips
>>  create mode 100644 meson-cross-mips.txt
>>
>> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> index 771143a9ea95..e390f8f472d5 100644
>> --- a/.gitlab-ci.yml
>> +++ b/.gitlab-ci.yml
>> @@ -90,6 +90,17 @@ build:tests-debian-meson-arm64:
>>      paths:
>>        - build
>>  
>> +build:tests-debian-meson-mips:
>> +  image: $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian-mips:latest
>> +  stage: build
>> +  script:
>> +    - export PKG_CONFIG_PATH=/usr/lib/mips-linux-gnu/pkgconfig/
>> +    - meson --cross-file meson-cross-mips.txt build
>> +    - ninja -C build
>> +  artifacts:
>> +    paths:
>> +      - build
>> +
>>  build:tests-debian-autotools:
>>    image: $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian:latest
>>    stage: build
>> @@ -221,6 +232,23 @@ containers:igt-debian-arm64:
>>      - docker build -t $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian-arm64 -f Dockerfile.debian-arm64 .
>>      - docker push $CI_REGISTRY/$CI_PROJECT_PATH/igt-debian-arm64
> 
> Any particular reason for not having ninja-test step for MIPS?

Sorry I overlooked that bit, I'm adding it in a v3.  That made me
realise that the libatomic1:mips package was required for
run-time linking on multi-arch file systems.

> Other than that (and Petri's concern, since I don't speak Debian),
> looks good.

Thanks, I also replied on the other thread about adding
libatomic1 for sub-architectures.

Guillaume
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-06-18 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 14:01 [Intel-gfx] [PATCH i-g-t v2] gitlab-ci: add build for MIPS Guillaume Tucker
2019-06-13 14:01 ` [igt-dev] " Guillaume Tucker
2019-06-14 10:02   ` Petri Latvala
2019-06-14 10:33   ` Arkadiusz Hiler
2019-06-18 11:27     ` Guillaume Tucker [this message]
2019-06-13 17:14 ` [igt-dev] ✓ Fi.CI.BAT: success for gitlab-ci: add build for MIPS (rev2) Patchwork
2019-06-15  5:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0085aaa7-1c75-524b-c74c-955f862cc931@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox