All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/libconfuse
Date: Thu, 22 Jan 2009 10:05:50 +0100	[thread overview]
Message-ID: <878wp3pv69.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090122071406.155456d9@hcegtvedt> (Hans-Christian Egtvedt's message of "Thu\, 22 Jan 2009 07\:14\:06 +0100")

>>>>> "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

      parent reply	other threads:[~2009-01-22  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=878wp3pv69.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.