dev-util/valgrind says: Valgrind will not work if glibc does not have debug symbols. To fix this you can add splitdebug to FEATURES in make.conf. and remerge glibc. However, I get "internal file collisions" when I actually add FEATURES="splitdebug". * Package 'sys-libs/glibc-2.29-r7' has internal collisions between non- * identical files (located in separate directories in the installation * image (${D}) corresponding to merged directories in the target * filesystem (${ROOT})): * * /usr/lib/debug/usr/lib64/Mcrt1.o.debug * /usr/lib/debug/usr/lib/Mcrt1.o.debug * /usr/lib/debug/usr/lib64/Mcrt1.o.debug * Differences: size, content * * /usr/lib/debug/usr/lib64/Scrt1.o.debug * /usr/lib/debug/usr/lib/Scrt1.o.debug * /usr/lib/debug/usr/lib64/Scrt1.o.debug * Differences: size, content * * /usr/lib/debug/usr/lib64/audit/sotruss-lib.so.debug * /usr/lib/debug/usr/lib/audit/sotruss-lib.so.debug * /usr/lib/debug/usr/lib64/audit/sotruss-lib.so.debug * Differences: size, content * I guess this more likely is a portage issue rather than a glibc one, but not completely sure.
Created attachment 599126 [details] emerge-info
Created attachment 599128 [details] build.log
Your profile is default/linux/amd64/17.1/desktop/plasma/systemd. Do you have /usr/lib and /usr/lib64 being different directories? Please post your output of: $ ls -ld /usr/lib* /lib*
I do not know if making /usr/lib/debug/usr/lib a symlink to lib64 (/usr/lib/debug/usr/lib64) was standard practice in 17.0 profiles. In 17.1 profiles, these directories (/usr/lib/debug/usr/lib and /usr/lib/debug/usr/lib64) should certainly be separate. You can do the following: 1. Delete /usr/lib/debug/lib symlink (if it exists as symlink). 2. Delete /usr/lib/debug/usr/lib symlink. 3. Rebuild all packages which are registered as installing /usr/lib/debug/lib or /usr/lib/debug/usr/lib. Find them using: $ cd /var/db/pkg $ grep -l /usr/lib/debug/lib/ */*/CONTENTS $ grep -l /usr/lib/debug/usr/lib/ */*/CONTENTS
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > You can do the following: > 1. Delete /usr/lib/debug/lib symlink (if it exists as symlink). > 2. Delete /usr/lib/debug/usr/lib symlink. > 3. Rebuild all packages which are registered as installing > /usr/lib/debug/lib or /usr/lib/debug/usr/lib. Find them using: > $ cd /var/db/pkg > $ grep -l /usr/lib/debug/lib/ */*/CONTENTS > $ grep -l /usr/lib/debug/usr/lib/ */*/CONTENTS Actually it could result in orphaned files (located in /usr/lib/debug/{,usr/}lib64 but previously registered in /usr/lib/debug/{,usr/}lib), so better to delete whole /usr/lib/debug: 1. Delete /usr/lib/debug 2. Rebuild all packages registered as installing /usr/lib/debug: $ cd /var/db/pkg $ grep -l /usr/lib/debug/ */*/CONTENTS
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #5) > 2. Rebuild all packages registered as installing /usr/lib/debug: > $ cd /var/db/pkg > $ grep -l /usr/lib/debug/ */*/CONTENTS Simpler command: emerge -1 /usr/lib/debug
Maintainer of app-portage/unsymlink-lib can decide if app-portage/unsymlink-lib should handle /usr/lib/debug/{,usr/}lib* or not.
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #7) > Maintainer of app-portage/unsymlink-lib can decide if > app-portage/unsymlink-lib should handle /usr/lib/debug/{,usr/}lib* or not. Please file a separate bug. I'd like to focus on restoring user's system in this bug.
