All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Mathias Rudnik <rudnik.mathias@googlemail.com>,
	Yocto Project <yocto@yoctoproject.org>
Subject: Re: Error do_compile libepoxy
Date: Fri, 19 Jan 2018 09:45:10 +0200	[thread overview]
Message-ID: <28c69ac5-219a-8718-83f6-5f7f2b51bf10@linux.intel.com> (raw)
In-Reply-To: <CAJ86T=U4m-J8WLdRP6UFP7T=FxyRRMsc7uXzpOyU9uCoimA1_g@mail.gmail.com>

On 01/19/2018 05:29 AM, Andre McCurdy wrote:
>> Note that this same test does build fine in poky, so disabling the tests is
>> not a good fix. You should figure out what is about the non-poky EGL headers
>> that is causing the failure, and whether you need to configure the provider
>> of those headers differently, or add missing dependencies etc.
> 
> Upstream documents that the test suite relies on X11:
> 
>    https://github.com/anholt/libepoxy/blob/1.4.3/README.md#building
> 
> So disabling the test suite for targets without X11 seems like a
> perfectly reasonable approach.

The meson.build files already have guards for lack of X11 around the 
test files that are failing here. It looks like in this particular 
configuration meson erroneously detects that X11 is present, when it's not.

Alex


  reply	other threads:[~2018-01-19  7:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 12:46 Error do_compile libepoxy Mathias Rudnik
2018-01-17 12:53 ` Burton, Ross
2018-01-17 12:58 ` Andrea Galbusera
2018-01-18  8:58   ` Andrea Galbusera
2018-01-18  9:05     ` Alexander Kanavin
2018-01-18 10:00       ` Martin Jansa
2018-01-18 10:57         ` Alexander Kanavin
2018-01-18 13:13       ` Max Krummenacher
2018-01-18 13:41         ` Andrea Galbusera
2018-01-18 13:49           ` Alexander Kanavin
2018-01-19  3:29             ` Andre McCurdy
2018-01-19  7:45               ` Alexander Kanavin [this message]
2018-01-19 10:45                 ` Andrea Galbusera
2018-01-19 12:32                   ` Alexander Kanavin
2018-01-19 16:36                     ` Andrea Galbusera
2018-01-22 13:08                       ` Alexander Kanavin
2018-01-20  9:29                     ` Anuj Mittal
2018-01-20 17:07                       ` Andrea Galbusera
2018-01-21 15:23                         ` Anuj Mittal
2018-01-22  9:12                           ` Andrea Galbusera
2018-01-22 13:59                             ` Trevor Woerner
2018-01-18 14:08       ` Trevor Woerner
2018-01-18 15:05         ` Michael Gloff
2018-01-18 20:48           ` Trevor Woerner
2018-01-19  1:35             ` Michael Gloff
2018-01-18  9:09     ` Burton, Ross
  -- strict thread matches above, loose matches on Subject: below --
2018-01-12 13:39 Mathias Rudnik
2018-01-11 19:18 Mathias Rudnik
2018-01-14 20:05 ` Trevor Woerner

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=28c69ac5-219a-8718-83f6-5f7f2b51bf10@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=armccurdy@gmail.com \
    --cc=rudnik.mathias@googlemail.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.