Summary: | xmms not building (gcc 3.3.1) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chuck Brewer <cbrewer> |
Component: | Current packages | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chuck Brewer
2003-09-15 00:00:42 UTC
I'm sorry, how is bug #24379 relevant? I receive neither illegal instructions, nor am I in doubt about the arch of my cpu. As a matter of fact, that was the only package I had that DID fail to build w/3.3. Also of note is that my flags never failed to build any package for nigh on a year now, but all of a sudden 3.2 -> 3.3 causes a lone build to drop assembler messages and it's my flags? That's akin to saying that the toast went though the ceiling because I set my toaster settings wrong, when the fault is in the toaster itself. I disagree with the closing as invalid, because it is a legitimate bug, however if devs will not take a bug report because it contains -march=k6* (if if the sources getting built contain more radical flags that what I've assigned) I think marking them wontfix with a note to take it up with the gcc people would be more descriptive than "invalid". Also a note on -dev/-user letting people know you wont take their bugs seriously if submitted with k6 flags, though that might drop your prospective reporters/fixers by 20% or so... |