This bug is used for the tracking of packages broken by the upcoming GCC 4.6, which has now entered the pre-release stage.
- File a NEW bug for each issue and make it BLOCK this one. Assign these bugs
to the maintainer of the package in question, NOT firstname.lastname@example.org please.
- Bugs filed without patches will be closed as INVALID.
- Don't use this bug for issues in GCC 4.6 itself. File a new bug and assign
it to the toolchain team.
- Please keep this tracker free from comments. Discussion should take place
on the relevant bugs.
GCC 4.6.0 released
(In reply to comment #2)
> gcc-4.6.1 released
No. Only gcc-4.6.0 released according to http://gcc.gnu.org/
gcc-4.6.1 released, according to gcc.gnu.org
See the comment about no comments.
*** Bug 382107 has been marked as a duplicate of this bug. ***
I just realized we need gcc-config-1.5 keyworded for Go support. Can we do that or should I backport it to 1.4?
*** Bug 407293 has been marked as a duplicate of this bug. ***
Why ~amd64 keyword is not present in ebuilds
I don't see amd64 specific bugs...
app-office/calligra-2.4.1 also fails:
calligra-2.4.1/filters/words/msword-odf/wv2/src/textconverter.cpp:65:5: error: 'iconv_t' does not name a type
alligra-2.4.1/filters/words/msword-odf/wv2/src/textconverter.cpp: In constructor 'wvWare::TextConverter::Private::Private(const string&, const string&)':
calligra-2.4.1/filters/words/msword-odf/wv2/src/textconverter.cpp:44:53: error: class 'wvWare::TextConverter::Private' does not have any field named 'm_iconv'
I just stumbled accross the gcc site and see that gcc-4.5 is no longer maintained. Maybe there is a way to make software packages, which refuse to compile with an recent version of gcc, require a older gcc, while unmasking a newer one for default?