On Sun, Jul 05, 2009 at 06:56:41PM +0300, Pauli Nieminen wrote:
@@ -124,6 +129,10 @@ AC_CACHE_CHECK([for supported warning flags],
libdrm_cv_warn_cflags, [
AC_MSG_CHECKING([which warning flags were supported])])
WARN_CFLAGS=$libdrm_cv_warn_cflags
+if test x$STRICT_COMPILE = xyes;
On Sat, Jul 4, 2009 at 2:37 AM, Pauli Nieminensuok...@gmail.com wrote:
This might also require -std=c99 to set c standard correctly. I did
use that in my CFLAGS when I tried to compile with -Werror.
New version of patch attached to add the -std=c99 if using strict compilation
From
On Sun, Jul 5, 2009 at 6:53 PM, Pauli Nieminensuok...@gmail.com wrote:
On Sat, Jul 4, 2009 at 2:37 AM, Pauli Nieminensuok...@gmail.com wrote:
This might also require -std=c99 to set c standard correctly. I did
use that in my CFLAGS when I tried to compile with -Werror.
New version of patch
---
configure.ac | 11 ++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/configure.ac b/configure.ac
index be2fbbf..763464b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -52,6 +52,11 @@ AC_ARG_ENABLE(radeon-experimental-api,
[Enable support for radeon's
This might also require -std=c99 to set c standard correctly. I did
use that in my CFLAGS when I tried to compile with -Werror.
--
--
___
Dri-devel mailing list
