Re: [gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-16 Thread Paul de Vrieze
On Monday 10 July 2006 01:51, Ryan Hill wrote: No, that would be a major pain in the ass for anyone wanting to use -fast-math, which does have legitimate uses. I want to pose here that -ffast-math has NO LEGITIMATE use as a global CFLAG. In some apps it doesn't matter as they don't use math.

Re: [gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-16 Thread Paul de Vrieze
On Tuesday 11 July 2006 04:32, Ryan Hill wrote: If yes, why ? And what is your better idea ? I prefer a filter-flags with a ewarn (or elog, haven't read that thread yet ;)) message. * The -ffast-math option is known to break this package and has been filtered from your CFLAGS. Link to

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-16 Thread Ryan Hill
Paul de Vrieze wrote: My argument is that we must not filter -ffast-math or any other dangerous cflags. The reason being that people will request more filters for all packages that don't work with it. Many users will either ignore or miss the warning messages. Filtering the flag basically

Re: [gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-15 Thread Denis Dupeyron
On 7/11/06, Ryan Hill [EMAIL PROTECTED] wrote: Their phrase, not mine. ;) I think the idea is you should be able to emerge -e world and walk away and not have anything interrupt the process thus requiring the user interact with the system. Well yes, but an ebuild that dies, whatever the

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-15 Thread Ryan Hill
Denis Dupeyron wrote: Well yes, but an ebuild that dies, whatever the reason, hasn't much to do with interactivity. Fine. Call it the don't-kill-the-emerge-for-silly-reasons philosophy if you like. I personally don't prefer it, but a lot of people think it's a good idea. What will follow

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-15 Thread Ryan Hill
Ryan Hill wrote: 2.95.3, 3.1.1, 3.2.2, 3.2.3, 3.3.2, 3.3.5, 3.3.6, 3.4.1, 3.4.4, 3.4.5, 3.4.6, My bad, 3.2.2 is masked for everyone ATM. --de. signature.asc Description: OpenPGP digital signature

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-11 Thread Ryan Hill
Denis Dupeyron wrote: Correct me if I'm wrong, but this has nothing to do with being interactive or not. To me, an ebuild that dies (intentionally or due to a build error) isn't interactive at all. Their phrase, not mine. ;) I think the idea is you should be able to emerge -e world and walk

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-10 Thread Duncan
Denis Dupeyron [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sun, 09 Jul 2006 23:24:24 +0200: In bug #139412, I ask Paul de Vriese why he thinks python should die on --fast-math instead of just filtering it. Here's his answer : Denis, quite simple. -ffast-math is broken

Re: [gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-10 Thread Denis Dupeyron
On 7/10/06, Ryan Hill [EMAIL PROTECTED] wrote: Ebuilds shouldn't die on anything according to the non-interactive portage philosophy. I don't know how official that philosophy is though. Correct me if I'm wrong, but this has nothing to do with being interactive or not. To me, an ebuild that

[gentoo-dev] Re: Dying on some CFLAGS instead of filtering them.

2006-07-09 Thread Ryan Hill
Denis Dupeyron wrote: In bug #139412, I ask Paul de Vriese why he thinks python should die on --fast-math instead of just filtering it. Here's his answer : Denis, quite simple. -ffast-math is broken and short-sighted for a global flag. Filtering gives the shortsighted message that it works