Attachment 58502 Details for Bug 47345 – configure: Keep passed-in CFLAGS for DRI tests

[patch] configure: Keep passed-in CFLAGS for DRI tests

0001-configure-Keep-passed-in-CFLAGS-for-DRI-tests.patch (text/plain), 1.33 KB, created by Thierry Reding on 2012-03-15 05:16:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Thierry Reding

Created: 2012-03-15 05:16:53 UTC

Size: 1.33 KB

patch

obsolete

>From a2d12914af20e8644b059a54192a90da6ddc9f06 Mon Sep 17 00:00:00 2001
>From: Thierry Reding <thierry.reding@avionic-design.de>
>Date: Thu, 15 Mar 2012 13:10:20 +0100
>Subject: [PATCH] configure: Keep passed-in CFLAGS for DRI tests
>
>When the user passes extra CFLAGS and CPPFLAGS to the configure script,
>they should be kept when performing subsequent checks with additional
>flags. This is required to properly build in cross-compilation setups
>where the user may pass in flags like --sysroot in order to pick up the
>cross-built dependencies.
>
>Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
>---
> configure.ac |    4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/configure.ac b/configure.ac
>index 03a35bd..7ca3075 100644
>--- a/configure.ac
>+++ b/configure.ac
>@@ -192,8 +192,8 @@ sdkdir=`$PKG_CONFIG --variable=sdkdir xorg-server`
> if test "x$enable_dri" != "xno"; then
>         save_CFLAGS="$CFLAGS"
>         save_CPPFLAGS="$CPPFLAGS"
>-        CFLAGS="$XORG_CFLAGS $DRI_CFLAGS $DRM_CFLAGS"
>-        CPPFLAGS="$XORG_CFLAGS $DRI_CFLAGS $DRM_CFLAGS"
>+        CFLAGS="$CFLAGS $XORG_CFLAGS $DRI_CFLAGS $DRM_CFLAGS"
>+        CPPFLAGS="$CPPFLAGS $XORG_CFLAGS $DRI_CFLAGS $DRM_CFLAGS"
>         AC_CHECK_HEADERS([dri.h sarea.h dristruct.h],, [DRI=no],
>                 [/* for dri.h */
>                  #include <xf86str.h>
>-- 
>1.7.9.4
>

Actions: View | Splinter Review

Attachments on bug 47345: 58491 | 58492 | 58493 | 58494 | 58502

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.