Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] support/dependencies: add check for c++ multilib
Date: Tue, 6 Feb 2018 23:00:04 +0100	[thread overview]
Message-ID: <20180206220004.GD28439@scaer> (raw)
In-Reply-To: <20180205215708.16363-1-gael.portay@savoirfairelinux.com>

Ga?l, All,

On 2018-02-05 16:57 -0500, Ga?l PORTAY spake thusly:
> Some packages build C++ 32bits host-tools and need the g++-multilib to
> be installed on the build machine. As example, qt5webengine builds a C++
> host-tool when target is 32bits.
> 
> Add the check for g++-multilib to the dependencies script; and update
> the Dockerfile to install g++-multilib package.
> 
> Signed-off-by: Ga?l PORTAY <gael.portay@savoirfairelinux.com>

So, this patch was applied, but there is some second-thoughts about it,
especially since not al our autobuilders have g++-multilib for now...

But my concern so far is just about the Dockerfile, see below...

> diff --git a/support/docker/Dockerfile b/support/docker/Dockerfile
> index 474e073c61..ce3fdd9cc2 100644
> --- a/support/docker/Dockerfile
> +++ b/support/docker/Dockerfile
> @@ -22,7 +22,7 @@ COPY apt-sources.list /etc/apt/sources.list
>  RUN dpkg --add-architecture i386 && \
>      apt-get update -y && \
>      apt-get install -y --no-install-recommends \
> -        build-essential cmake libc6:i386 gcc-multilib \
> +        build-essential cmake libc6:i386 g++-multilib \
>          bc ca-certificates file locales rsync \
>          cvs bzr git mercurial subversion wget \
>          cpio unzip \

So, we should not confuse the Dockerfile for what it is not: it is not
meant for user consumption; we never advertised it. Instead, it is only
for use by our gitlab-ci based runtime tests. As such, it should only
include what is needed in that context.

At least for now.

Maybe we will want to make it ready for public consumption later, but it
is not for now.

As such, I don't think we should have updated the dockerfile in the same
patch. Afterall, it is not a mandatory dependency; it is needed (as far
as I can understand) only for qt5webengine.

There are ther optional dependencies that are not in the dockerfile. For
example, we do not have a jave compiler, which is needed by a few
packages in Buildroot, but which are for now not tested by the gitlab-ci
jobs.

So, I would suggest we retract this change in the Dockerfile...

Thoughts from others? Arnout, Thomas, Peter?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2018-02-06 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 21:57 [Buildroot] [PATCH v2 1/1] support/dependencies: add check for c++ multilib Gaël PORTAY
2018-02-06 16:22 ` Thomas Petazzoni
2018-02-06 22:00 ` Yann E. MORIN [this message]
2018-02-07 19:47   ` Gaël PORTAY

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=20180206220004.GD28439@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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