#366 closed defect (fixed)
c++filt installation problem
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | highest | Milestone: | |
| Component: | Book | Version: | CVS |
| Severity: | normal | Keywords: | |
| Cc: | gerard@… |
Description
gcc-3.1 will install its c++filt (version 3.1), and binutil-2.12.1 will install its c++filt (version 2.12.1), too. However, gcc 3 changes the C++ ABI and thus old version c++filt might not be able to demangle new ABI correctly.
As the book suggests, binutil is installed AFTER gcc, and the installation will overwrite new c++filt. You may like to fix this bug.
Attachments (2)
Change History (8)
by , 23 years ago
comment:1 by , 23 years ago
Regarding the test case + fix: why wait until sh-utils to run "mv c++filt.back c++filt" ?
comment:2 by , 22 years ago
so guys, are we going with making the gcc version of c++filt the default one? If so, I suggest we do the rename just before and after installing binutils - there's no reason I can see to do it at any other point.
comment:3 by , 22 years ago
| Cc: | added |
|---|
comment:5 by , 22 years ago
| Priority: | low → highest |
|---|
comment:6 by , 22 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
After discussing it, concensus is that it doesn't really matter much which one is used. The c++filt stuff from gcc and binutils are always synchronized whenever a new version of either package is released, so the current way (using binutils' version because it happens to be installed later than gcc) is good enough.
Confirm bug, suggest change, and ask for tests