From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qt5wayland: fix build issue with mesa3d w/out xcb
Date: Tue, 27 Feb 2018 23:39:39 +0100 [thread overview]
Message-ID: <20180227233939.2925e4dc@windsurf.lan> (raw)
In-Reply-To: <20180227222806.pzbq5wz6fftrxqj3@archlinux>
Hello,
On Tue, 27 Feb 2018 17:28:06 -0500, Ga?l PORTAY wrote:
> Peter Seiderer sent me an hint[1].
>
> I have to find time to send a proper patch. Do not worry, I have that
> fix in mind.
>
> Gael
>
> [1]: http://lists.busybox.net/pipermail/buildroot/2018-February/214210.html
Indeed, this hint looks good. It will be nice to have a better fix for
this.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-27 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 20:48 [Buildroot] [git commit] qt5wayland: fix build issue with mesa3d w/out xcb Peter Korsgaard
2018-02-27 22:11 ` Thomas Petazzoni
2018-02-27 22:28 ` Gaël PORTAY
2018-02-27 22:39 ` Thomas Petazzoni [this message]
2018-02-28 6:32 ` Peter Korsgaard
2018-02-28 11: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=20180227233939.2925e4dc@windsurf.lan \
--to=thomas.petazzoni@bootlin.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