gcc-4.1-multilib doesn't get installed on dist-upgrade to gutsy
Bug #153046 reported by
Olof Johansson
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gcc-4.1 (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Seems like gcc-4.1-multilib doesn't get automatically installed on a dist-upgrade from feisty to gutsy.
On PPC, this means that you can no longer build 64-bit programs that you used to, since the 64-bit libgcc.a was shipped in gcc-4.1 before. While it's no problem to manually install gcc-4.1-multilib, it's still unexpected behaviour.
Revision history for this message
| Matthias Klose (doko) wrote | #1 |
| Changed in gcc-4.1: | |
| importance: | Undecided → Low |
| status: | New → Won't Fix |
To post a comment you must log in.
There's no easy way to "fix" this. gcc-4.1 suggests gcc-4.1-multilib; we cannot recommend it, or else gcc-4.1-multilib is installed as a part of the "install recommends by default" specification. In feisty we had a dangling symlink in gcc-4.1 instead, when lib64gcc1 was not installed.
Best thing would be to install gcc-multilib so that the package is upgraded on a gutsy->hardy upgrade as well.
Closing this as wontfix.