From: Sergei Trofimovich <slyfox@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FYI: Rules for distro-friendly packages
Date: Sun, 27 Jun 2010 09:09:00 +0300 [thread overview]
Message-ID: <20100627090900.5378b5db@mosly> (raw)
In-Reply-To: <20100626195733.GF4789@nibiru.local>
On Sat, 26 Jun 2010 21:57:33 +0200
Enrico Weigelt <weigelt@metux.de> wrote:
> > > #2 One point i don't agree is the "dont add -Werror" rule. actually,
> > > i'm thinking of making -Wall and -Werror mandatory. if some
> > > package doenst build fine, it's simply broken. period.
> >
> > Uhm. No. Certain compilers will give you warnings for f(g(a), g(b)) if
> > you -Wall.
>
> Warn on what exactly ? Which compilers do that ?
I suggest you to try latest available dev-lang/icc (11.1.072).
This thing is really paranoid:
remark #2259: non-pointer conversion from "int" to "unsigned char" may lose significant bits
unsigned char BlinkerPhase = 0;
...
BlinkerPhase = (BlinkerPhase + 1) & 3;
remark #981: operands are evaluated in unspecified order (tons of them)
return strcmp( left.c_str(), right.c_str() ) > 0;
--
Sergei
next prev parent reply other threads:[~2010-06-27 6:09 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 20:17 [gentoo-dev] FYI: Rules for distro-friendly packages Enrico Weigelt
2010-06-25 20:28 ` Alistair Bush
2010-06-26 18:56 ` Enrico Weigelt
2010-06-25 21:00 ` Krzysztof Pawlik
2010-06-26 18:51 ` Enrico Weigelt
2010-06-26 19:21 ` Krzysztof Pawlik
2010-06-26 19:46 ` Enrico Weigelt
2010-06-26 19:59 ` Ciaran McCreesh
2010-06-26 20:08 ` Krzysztof Pawlik
2010-06-26 20:10 ` Enrico Weigelt
2010-06-26 20:09 ` Enrico Weigelt
2010-06-26 20:18 ` Ciaran McCreesh
2010-06-27 10:34 ` Enrico Weigelt
2010-06-27 10:45 ` Ciaran McCreesh
2010-06-27 11:08 ` Enrico Weigelt
2010-06-27 11:15 ` Ciaran McCreesh
2010-06-27 18:33 ` Brian Harring
2010-06-27 18:48 ` Patrick Lauer
2010-08-17 17:04 ` Enrico Weigelt
2010-08-18 4:15 ` Jacob Godserv
2010-08-18 19:10 ` Enrico Weigelt
2010-06-26 20:33 ` Nirbheek Chauhan
2010-06-27 10:35 ` Enrico Weigelt
2010-06-27 20:46 ` Nirbheek Chauhan
2010-06-27 5:48 ` Hans de Graaff
2010-06-25 22:24 ` Petteri Räty
2010-06-26 19:39 ` Enrico Weigelt
2010-06-26 19:50 ` Ciaran McCreesh
2010-06-26 19:57 ` Enrico Weigelt
2010-06-26 20:12 ` Ciaran McCreesh
2010-06-27 5:52 ` [gentoo-dev] " Nikos Chantziaras
2010-06-27 10:47 ` Enrico Weigelt
2010-06-27 11:56 ` Nikos Chantziaras
2010-06-27 12:23 ` Harald van Dijk
2010-06-27 12:25 ` Enrico Weigelt
2010-06-27 12:35 ` Ciaran McCreesh
2010-06-27 14:46 ` Nikos Chantziaras
2010-06-27 17:14 ` Harald van Dijk
2010-06-27 17:48 ` Nikos Chantziaras
2010-06-27 18:10 ` dev-random
2010-06-27 18:27 ` Nikos Chantziaras
2010-06-27 6:09 ` Sergei Trofimovich [this message]
2010-06-27 10:52 ` [gentoo-dev] " Enrico Weigelt
2010-06-27 11:28 ` Richard Freeman
2010-06-26 19:57 ` [gentoo-dev] " Nikos Chantziaras
2010-06-27 8:14 ` [gentoo-dev] " Rémi Cardona
2010-06-27 11:02 ` Enrico Weigelt
2010-06-27 12:13 ` Patrick Lauer
2010-06-27 12:22 ` Enrico Weigelt
2010-06-27 12:33 ` Ciaran McCreesh
2010-06-27 16:54 ` Rémi Cardona
2010-06-28 10:26 ` Enrico Weigelt
[not found] ` <201006252338.51889.alan.mckinnon@gmail.com>
2010-08-17 21:05 ` [gentoo-dev] Re: [gentoo-user] " Enrico Weigelt
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=20100627090900.5378b5db@mosly \
--to=slyfox@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox