From: Thierry Reding <thierry.reding@gmail.com>
To: igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 1/2] tests/testdisplay: Explicitly use GLIB_CFLAGS
Date: Mon, 5 Feb 2018 12:56:10 +0100 [thread overview]
Message-ID: <20180205115611.23230-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
testdisplay.h includes the glib.h header file but the Makefile does not
explicitly pass a -I option with the path containing that header, hence
causing the build to fail. Note that this doesn't seem to happen with a
recent enough version of cairo, which implicitly provides the correct
-I option.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
tests/Makefile.am | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/Makefile.am b/tests/Makefile.am
index 1b9a7b0a2311..8472a6bf0a73 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
@@ -149,6 +149,8 @@ kms_chamelium_LDADD = $(LDADD) $(XMLRPC_LIBS) $(LIBUDEV_LIBS)
audio_CFLAGS = $(AM_CFLAGS) $(ALSA_CFLAGS)
audio_LDADD = $(LDADD) $(ALSA_LIBS)
+testdisplay_CFLAGS = $(AM_CFLAGS) $(GLIB_CFLAGS)
+
amdgpu_amd_basic_CFLAGS = $(AM_CFLAGS) $(DRM_AMDGPU_CFLAGS)
amdgpu_amd_basic_LDADD = $(LDADD) $(DRM_AMDGPU_LIBS)
amdgpu_amd_cs_nop_CFLAGS = $(AM_CFLAGS) $(DRM_AMDGPU_CFLAGS)
--
2.15.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-02-05 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 11:56 Thierry Reding [this message]
2018-02-05 11:56 ` [Intel-gfx] [PATCH i-g-t 2/2] tools/intel_dp_compliance: Add missing GLIB_CFLAGS Thierry Reding
2018-02-05 12:30 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] tests/testdisplay: Explicitly use GLIB_CFLAGS Patchwork
2018-02-05 14:27 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-02-27 13:38 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2018-02-27 13:50 ` Arkadiusz Hiler
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=20180205115611.23230-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox