Summary: | toolchain.eclass should not overwrite bug URL if a gcc compiler crash occurred | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Eclasses | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2012-12-21 22:38:15 UTC
toolchain.eclass, lines 1900-, gcc_version_patch() there is no such thing as separate bug urls depending on the type of bug gcc itself hit. Gentoo is doing the correct thing and point users at the distro-specific bugzilla. expecting the upstream bugzilla is wrong. perhaps a gcc-specific page could be put together and we could point to that, but i don't really see much advantage. if you know wtf you're doing, then the bug url output from gcc is entirely useless -- you know where the right sites are what to report to each. if you have no idea wtf you're doing, then pointing to the main bugzilla page is correct. it has info for reporting bugs, searching for existing reports, and links to actually file new ones. the point of distros is to be the initial triage point, not for upstream to be. |