public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Weyershäuser" <thedude0001@gmx.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Another package that doesn't like GCC 4
Date: Thu, 23 Nov 2006 01:52:40 +0100	[thread overview]
Message-ID: <4564F0D8.8030904@gmx.de> (raw)
In-Reply-To: <20061122232205.GN11575@randombit.net>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Jack Lloyd wrote:
> I would think it would still be useful to have know, so the ebuild
> could use filter-flags to prevent this problem from occuring for
> others (if it is in fact a CFLAGS problem).

It might depend on the flag we're talking about, but filter-flags and
replace-flags is mostly used for ebuilds that don't work with supported
flags (like an ebuild that doesn't like -Os but needs -O2). There has
been a debate a couple of weeks back if ebuilds should even filter
-ffast-math as this is a flag that breaks dozens of packages, sometimes
in sneaky, hard-to-debug ways, or if the ebuild should just die if it
finds that flag.

You're free to try, but the idea is that while you have a lot of choices
when using Gentoo it is not the devs duty to stop you from making bad
choices or protect you from their effects.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-11-23  0:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 16:28 [gentoo-amd64] Another package that doesn't like GCC 4 Peter Humphrey
2006-11-22 17:38 ` Hemmann, Volker Armin
2006-11-22 18:39 ` Michael Weyershäuser
2006-11-22 23:22   ` Jack Lloyd
2006-11-23  0:52     ` Michael Weyershäuser [this message]
2006-11-23  6:47       ` [gentoo-amd64] " Duncan
2006-11-23 11:39 ` [gentoo-amd64] " Peter Humphrey
2006-11-23 12:58   ` Jan Jitse Venselaar
2006-11-23 16:03     ` Peter Humphrey
2006-11-23 19:21     ` [gentoo-amd64] " Duncan

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=4564F0D8.8030904@gmx.de \
    --to=thedude0001@gmx.de \
    --cc=gentoo-amd64@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