P.S. I guess I was thinking of "the package of gcc that is shipped in Fedora" as being one of the subjects of this ticket, more than "gcc itself". I figured it might help other people to understand that if they are seeing these errors, it is the combination of gcc 4.7.0 pre-release and their other packages that results in the errors. But again, I didn't intend to say that the errors were caused by gcc having a bug. Also, of course, Crypto++ and quite a few other packages are also the subjects of this issue. The launchpad ticket -- https://bugs.launchpad.net/gcc/+bug/915018 -- has links to relevant tickets in various issue trackers.
For my own future reference:
1. Is there a way to express in bugzilla.redhat.com that an issue affects a package of software $X version $Y within Fedora release $Z? Ideally I would have said "This is an issue you may have if you're using the 4.7.0 pre-release distributed in Fedora Rawhide.". Is there a way to express that in the bugzilla db?
2. Is there a way to denote "This is an issue that affects $X or that the presence of $X can trigger, but is not a bug in $X?".
P.S. I guess I was thinking of "the package of gcc that is shipped in Fedora" as being one of the subjects of this ticket, more than "gcc itself". I figured it might help other people to understand that if they are seeing these errors, it is the combination of gcc 4.7.0 pre-release and their other packages that results in the errors. But again, I didn't intend to say that the errors were caused by gcc having a bug. Also, of course, Crypto++ and quite a few other packages are also the subjects of this issue. The launchpad ticket -- https:/ /bugs.launchpad .net/gcc/ +bug/915018 -- has links to relevant tickets in various issue trackers.
For my own future reference:
1. Is there a way to express in bugzilla.redhat.com that an issue affects a package of software $X version $Y within Fedora release $Z? Ideally I would have said "This is an issue you may have if you're using the 4.7.0 pre-release distributed in Fedora Rawhide.". Is there a way to express that in the bugzilla db?
2. Is there a way to denote "This is an issue that affects $X or that the presence of $X can trigger, but is not a bug in $X?".
Thanks!