Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] svn commit: trunk/buildroot/package/libconfuse
@ 2009-01-21 20:45 jacmet at uclibc.org
  2009-01-22  6:14 ` Hans-Christian Egtvedt
  0 siblings, 1 reply; 4+ messages in thread
From: jacmet at uclibc.org @ 2009-01-21 20:45 UTC (permalink / raw)
  To: buildroot

Author: jacmet
Date: 2009-01-21 20:45:10 +0000 (Wed, 21 Jan 2009)
New Revision: 24944

Log:
libconfuse: fix build by removing -Werror flag

Added:
   trunk/buildroot/package/libconfuse/libconfuse-2.6-dont-use-werror.patch


Changeset:
Added: trunk/buildroot/package/libconfuse/libconfuse-2.6-dont-use-werror.patch
===================================================================
--- trunk/buildroot/package/libconfuse/libconfuse-2.6-dont-use-werror.patch	                        (rev 0)
+++ trunk/buildroot/package/libconfuse/libconfuse-2.6-dont-use-werror.patch	2009-01-21 20:45:10 UTC (rev 24944)
@@ -0,0 +1,34 @@
+confuse: don't compile with -Werror
+
+Werror isn't really a robust setting for !development.
+---
+ src/Makefile.am |    2 +-
+ src/Makefile.in |    2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+Index: confuse-2.6/src/Makefile.am
+===================================================================
+--- confuse-2.6.orig/src/Makefile.am
++++ confuse-2.6/src/Makefile.am
+@@ -10,7 +10,7 @@
+ DEFS = -DLOCALEDIR=\"$(localedir)\" @DEFS@
+ 
+ if cc_is_gcc
+-AM_CFLAGS=-Wall -Werror
++AM_CFLAGS=-Wall
+ endif
+ 
+ LIBS = @LIBS@
+Index: confuse-2.6/src/Makefile.in
+===================================================================
+--- confuse-2.6.orig/src/Makefile.in
++++ confuse-2.6/src/Makefile.in
+@@ -196,7 +196,7 @@
+ libconfuse_la_SOURCES = confuse.c lexer.l
+ libconfuse_la_LIBADD = $(LTLIBINTL)
+ include_HEADERS = confuse.h
+- at cc_is_gcc_TRUE@AM_CFLAGS = -Wall -Werror
++ at cc_is_gcc_TRUE@AM_CFLAGS = -Wall
+ CLEANFILES = *~ \#*\#
+ AM_LFLAGS = -Pcfg_yy -olex.yy.c
+ all: all-am

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] svn commit: trunk/buildroot/package/libconfuse
  2009-01-21 20:45 [Buildroot] svn commit: trunk/buildroot/package/libconfuse jacmet at uclibc.org
@ 2009-01-22  6:14 ` Hans-Christian Egtvedt
  2009-01-22  8:47   ` Sven Neumann
  2009-01-22  9:05   ` Peter Korsgaard
  0 siblings, 2 replies; 4+ messages in thread
From: Hans-Christian Egtvedt @ 2009-01-22  6:14 UTC (permalink / raw)
  To: buildroot

On Wed, 21 Jan 2009 20:45:12 +0000 (UTC)
jacmet at uclibc.org wrote:

> Author: jacmet
> Date: 2009-01-21 20:45:10 +0000 (Wed, 21 Jan 2009)
> New Revision: 24944
> 
> Log:
> libconfuse: fix build by removing -Werror flag
> 

You know that is not fixing it ;) Source code should not generate
warnings, they are usually a sign of something bad is happening.

But I guess this is fine for now.

<snipp>

-- 
Best regards,
Hans-Christian Egtvedt

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] svn commit: trunk/buildroot/package/libconfuse
  2009-01-22  6:14 ` Hans-Christian Egtvedt
@ 2009-01-22  8:47   ` Sven Neumann
  2009-01-22  9:05   ` Peter Korsgaard
  1 sibling, 0 replies; 4+ messages in thread
From: Sven Neumann @ 2009-01-22  8:47 UTC (permalink / raw)
  To: buildroot

Hi,

On Thu, 2009-01-22 at 07:14 +0100, Hans-Christian Egtvedt wrote:
> On Wed, 21 Jan 2009 20:45:12 +0000 (UTC)
> jacmet at uclibc.org wrote:
> 
> > Author: jacmet
> > Date: 2009-01-21 20:45:10 +0000 (Wed, 21 Jan 2009)
> > New Revision: 24944
> > 
> > Log:
> > libconfuse: fix build by removing -Werror flag
> > 
> 
> You know that is not fixing it ;) Source code should not generate
> warnings, they are usually a sign of something bad is happening.

Source code that compiles without warnings on one compiler may generate
warnings on a different compiler (or just a different version or a
slightly differently configured instance of the very same compiler).
Having -Werror in public source code is always wrong as you can't
possibly know that it will compile cleanly for everyone.

And there are tons of warnings created by compilers that don't
necessarily indicate a problem in the source code. But of course you are
right that one should always check every warning carefully.


Sven

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] svn commit: trunk/buildroot/package/libconfuse
  2009-01-22  6:14 ` Hans-Christian Egtvedt
  2009-01-22  8:47   ` Sven Neumann
@ 2009-01-22  9:05   ` Peter Korsgaard
  1 sibling, 0 replies; 4+ messages in thread
From: Peter Korsgaard @ 2009-01-22  9:05 UTC (permalink / raw)
  To: buildroot

>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:

 >> libconfuse: fix build by removing -Werror flag
 >> 

 Hans-Christian> You know that is not fixing it ;) Source code should
 Hans-Christian> not generate warnings, they are usually a sign of
 Hans-Christian> something bad is happening.

 Hans-Christian> But I guess this is fine for now.

True, but in this case it's a simple warning about an unused variable.

Imho, shipping with -Werror isn't really a robust thing to do.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-01-22  9:05 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-21 20:45 [Buildroot] svn commit: trunk/buildroot/package/libconfuse jacmet at uclibc.org
2009-01-22  6:14 ` Hans-Christian Egtvedt
2009-01-22  8:47   ` Sven Neumann
2009-01-22  9:05   ` Peter Korsgaard

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox