From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/wayland: don't build tests
Date: Sun, 5 Mar 2017 14:21:02 +0100 [thread overview]
Message-ID: <20170305142102.0faed242@free-electrons.com> (raw)
In-Reply-To: <59483ee76c501ec78cfbb2250c3fbcf02f6f7a85.1488711390.git.yann.morin.1998@free.fr>
Hello,
On Sun, 5 Mar 2017 11:56:51 +0100, Yann E. MORIN wrote:
> wayland is entirely written in C, except for a single test that is
> written in C++.
>
> Since we are not interested in running the tests on the target, add an
> option to configure to disable tests altogether.
>
> Fixes:
> http://autobuild.buildroot.org/results/291/291e0f1ea18004190ae5acd9bec147cacc3e4bda/
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I think this solves our (Buildroot) immediate problem, but is not the
completely correct fix for upstream. Indeed, if Wayland is trying to
build some C++ code, it should use AC_PROG_CXX and then only try to
build the C++ code if it found a C++ compiler.
But well, this --disable-tests thing is definitely good enough for us,
so I'll apply this.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-05 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 10:56 [Buildroot] [PATCH 0/2] package/wayland: disable building tests Yann E. MORIN
2017-03-05 10:56 ` [Buildroot] [PATCH 1/2] package/wayland: drop non-existing configure option Yann E. MORIN
2017-03-05 10:56 ` [Buildroot] [PATCH 2/2] package/wayland: don't build tests Yann E. MORIN
2017-03-05 13:21 ` Thomas Petazzoni [this message]
2017-03-05 13:46 ` Yann E. MORIN
2017-03-05 15:35 ` [Buildroot] [PATCH 0/2] package/wayland: disable building tests Thomas Petazzoni
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=20170305142102.0faed242@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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