mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Stadler <sa.musl@univie.ac.at>
To: musl@lists.openwall.com
Subject: Re: Bug in include/netinet/in.h
Date: Thu, 24 Jan 2013 20:22:03 +0100	[thread overview]
Message-ID: <510189DB.6070106@univie.ac.at> (raw)
In-Reply-To: <20130123171138.GT20323@brightrain.aerifal.cx>

Am 23.01.2013 18:11, schrieb Rich Felker:
> On Wed, Jan 23, 2013 at 05:58:13PM +0100, John Spencer wrote:
>> On 01/23/2013 05:39 PM, Alexander Stadler wrote:
>>> [-Werror=parentheses]
>>> /space/build-trunk/trunk/build_dir/target-mips_r2_musl-0.9.8/netifd-2013-01-22.1/interface-ip.c:655:2: error: suggest parentheses around arithmetic in operand of '|' [-Werror=parentheses]
>>> cc1: all warnings being treated as errors
>> the bug here is -Werror being passed to the compiler, try adding
>> --disable-werror to the configure invocation
>>
>> (note: using -Werror by default is pretty inept, since it will cause
>> build errors on any compiler/libc combination that has not yet been
>> tested by the package author)
> 
> Normally these kind of warnings are ignored in the system headers and
> macro text expanded from macros defined in the system headers. I don't
> see any reason we can't "fix" this particular macro however if for
> some reason it's still making trouble..
> 
> Rich

I removed -Werror from CMakeLists.txt of netifd, after that it compiled (with warnings ;-) ).
Thank you!

(only size shocked me - 450KB (one day before with uClibc 50KB :-/ ))


  reply	other threads:[~2013-01-24 19:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 16:39 Alexander Stadler
2013-01-23 16:58 ` John Spencer
2013-01-23 17:08   ` Alexander Stadler
2013-01-23 17:11   ` Rich Felker
2013-01-24 19:22     ` Alexander Stadler [this message]
2013-01-24 20:38       ` Rich Felker
2013-01-24 20:46       ` John Spencer
2013-01-29 17:37         ` Alexander Stadler
2013-01-29 18:10           ` Szabolcs Nagy
2013-01-29 18:33             ` Alexander Stadler
2013-01-29 20:36               ` Florian Fainelli

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=510189DB.6070106@univie.ac.at \
    --to=sa.musl@univie.ac.at \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).