Summary: | perl, libperl gets screwed by -fsched2-use-superblocks; a case for flag-o-matic? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sg313 <sg313d> |
Component: | [OLD] Core system | Assignee: | Gentoo Perl team <perl> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | jakub |
Priority: | Highest | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Filters -fsched2-use-superblocks for perl
Filters -fsched2-use-superblocks for libperl |
Description
sg313
2006-08-14 09:47:00 UTC
Created attachment 94253 [details, diff]
Filters -fsched2-use-superblocks for perl
s.o.
Created attachment 94254 [details, diff]
Filters -fsched2-use-superblocks for libperl
s.o.
Quite frankly, we really have better things to do that to filter whatever ultraweird flag that someone has stuck into his flags for whatever reason. How about that you filter it yourself? The report was not meant to be an offense. Discard it if you want; I just wanted to share the solution. Fixed in cvs. Thanks! |