| Summary: | libsigc++ does not compile with gcc 4.3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Carlos Manuelda <StormByte> |
| Component: | Current packages | Assignee: | GNOME C++ Bindings Maintainers (OBSOLETE) <gnome-mm+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 198121 | ||
| Attachments: | compilation log | ||
|
Description
David Carlos Manuelda
2008-04-02 17:58:10 UTC
Created attachment 148114 [details]
compilation log
See bug #203931 and bug #206063. libsigc++-2.2.2 compiles fine with gcc-4.3. 2.2.2 or later needs to go stable. That's not our call to make. I wasn't implying that libsigc++-2.2.2 needs to go stable. gcc-4.3 doesn't even have any keywords yet. I just wanted to let the reporter know that the newer libsigc++ compiles fine with gcc-4.3 or that there's a patch for libsigc++-2.0.18 in bug #206063. I apologize for the misunderstanding. Ok, so I wait the patch to be included in tree soon :) (In reply to comment #5) > Ok, so I wait the patch to be included in tree soon :) libsigc++-2.2.2 is already included in the tree at ~arch visibility... gcc-4.3.0 on the other hand is not even keyworded anywhere. You can't mix and match stuff like that and have a compiler that is not even become ~arch yet, to compile packages that are in stable... (In reply to comment #6) > (In reply to comment #5) > > Ok, so I wait the patch to be included in tree soon :) > > libsigc++-2.2.2 is already included in the tree at ~arch visibility... > gcc-4.3.0 on the other hand is not even keyworded anywhere. You can't mix and > match stuff like that and have a compiler that is not even become ~arch yet, to > compile packages that are in stable... > Yes, but what I meant is that in order to test (runtime behaviours and so on at least), is better when it compiles all :) I only want to test things as this is the only thing I can do for now to help a bit, and report every package that fails :) Already in portage. Please check with the toolchain people if they have/need a list of packages that need to be fixed or updated before they can unmask (and later on stabilize) gcc 4.3. Our work here is done :) |
