| Summary: | sys-devel/gcc-4.7.1: /sbin/fix_libtool_files.sh: No such file or directory | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alec Meyers <alecm_88> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | alecm_88 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Yes, the path changed. pkg_postrm() is cached when you build a package so eclass changes can be made without completely screwing up the removal of installed ebuilds. You're seeing the cached pkg_postrm() from the last time gcc was built. Your next build will have the correct path. If you hit any problems just run it manually. Thanks for the clarification! *** This bug has been marked as a duplicate of bug 420731 *** |
After updating gcc, I noticed that it said: ... * Running 'fix_libtool_files.sh 4.7.0' /var/tmp/portage/._unmerge_/sys-devel/gcc-4.7.0/temp/environment: line 4498: /sbin/fix_libtool_files.sh: No such file or directory >>> Regenerating /etc/ld.so.cache... ... I do have fix_libtool_files.sh, but it's in /usr: $ which fix_libtool_files.sh /usr/sbin/fix_libtool_files.sh Oddly, though, it does not seem to belong to any package. I currently have gcc 4.5.3-r2, 4.6.3 and 4.7.1 installed (4.6.3 is default) Reproducible: Didn't try