Summary: | sys-devel/binutils-2.15.92.0.2-r7 fails to call binutils-config | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anthony Gorecki <anthony> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | binutils-file-log |
Description
Anthony Gorecki
2005-04-05 21:29:53 UTC
how were you able to get a /etc/env.d/binutils/config-${CTARGET} file and have a broken system ? Here is a portion of the result of upgrading to this version of the package: --snip-- <<< sym /usr/bin/ld <<< sym /usr/bin/gprof <<< sym /usr/bin/c++filt <<< sym /usr/bin/as <<< sym /usr/bin/ar <<< sym /usr/bin/addr2line <<< dir /usr/share/doc/binutils-2.15.92.0.2-r1/opcodes <<< dir /usr/share/doc/binutils-2.15.92.0.2-r1/libiberty --snip-- <<< dir /usr/share/doc/binutils-2.15.92.0.2-r1 <<< dir /usr/i686-pc-linux-gnu/bin --- !empty dir /usr/share/man/man1 --- !empty dir /usr/share/man --snip-- As you can see, what it's unmerging would break the system. The above was taken from the end of the upgrade process, and since binutils-config was not called for whatever reason, the missing files were never recreated. To answer your question, I don't know. I wasn't monitoring the status of the merged files when I upgraded the package because I wasn't expecting it to break. I'll attach the file merging portion of the update. Created attachment 55433 [details]
binutils-file-log
no, those are supposed to be unmerged `binutils-config` replaces all of those files but for some reason, it was not executed on your system if you do `rm /etc/env.d/binutils/config-*` and then `emerge binutils`, does binutils-config get executed automatically ? Yes it does. ok ... well if you can track down why it didnt run the first time, please re-open with that info :/ |