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 2/2] package/wayland: don't build tests
Date: Sun, 5 Mar 2017 14:46:18 +0100	[thread overview]
Message-ID: <20170305134618.GE3671@free.fr> (raw)
In-Reply-To: <20170305142102.0faed242@free-electrons.com>

Thomas, All,

On 2017-03-05 14:21 +0100, Thomas Petazzoni spake thusly:
> 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.

They do use AC_PROG_CXX:

    https://cgit.freedesktop.org/wayland/wayland/tree/configure.ac#n29

But please note the comment just a few lines below:

    https://cgit.freedesktop.org/wayland/wayland/tree/configure.ac#n33

    # check if we have C++ compiler. This is hacky workaround,
    # for a reason why it is this way see
    # http://lists.gnu.org/archive/html/bug-autoconf/2010-05/msg00001.html
    have_cpp_compiler=yes

    if ! which "$CXX" &>/dev/null; then
        have_cpp_compiler=no
    fi

    AM_CONDITIONAL(ENABLE_CPP_TEST, test "x$have_cpp_compiler" = "xyes")

Alas, this does not work, because CXX is set to 'false' so the which
actually succeeds. One would need to actually call $CXX to see if it is
working.

I'll see to send another patch to this effect.

Yet, I think this --disable-tests is also good to upstream.

Regards,
Yann E. MORIN.

> 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

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-03-05 13:46 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
2017-03-05 13:46     ` Yann E. MORIN [this message]
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=20170305134618.GE3671@free.fr \
    --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