Bug 830214 – sys-libs/musl-1.2.2-r7 QA Notice: Found an absolute symlink in a library directory

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2021-12-29 08:59:21 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sys-libs/musl-1.2.2-r7 unspecified issue.
Discovered on: amd64 (internal ref: tinderbox_musl)

NOTE:
This machine uses MUSL libc
Unspecified issue means that there is an issue but the tinderbox is missing a bug template about it. The issue will be specified manually.

[Comment 1 Agostino Sarubbo 2021-12-29 08:59:24 UTC]

Created attachment 760705 [details]
build.log.xz

build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)

[Comment 2 Sam James 2021-12-29 09:01:38 UTC]

 * Final size of build directory: 22264 KiB (21.7 MiB)
 * Final size of installed tree:   5236 KiB ( 5.1 MiB)
 * QA Notice: Found an absolute symlink in a library directory:
 *            /lib/ld-musl-x86_64.so.1 -> /usr/lib/libc.so
 *            It should be a relative symlink if in the same directory
 *            or a linker script if it crosses the /usr boundary.
 * QA Notice: Pre-stripped files found:
 * /usr/lib/crtn.o

/etc/portage/bashrc: line 31: enalyze: command not found

[Comment 3 Agostino Sarubbo 2021-12-29 09:09:47 UTC]

(In reply to Sam James from comment #2)
> /etc/portage/bashrc: line 31: enalyze: command not found

This is something that comes from the system, so please ignore it.

[Comment 4 Sam James 2022-01-01 04:09:53 UTC]

Pasting from #gentoo-hardened so I don't forget:
[18:50:41]  <@blueness> sam_, regarding bug 830214.  You can try to remove the abs sym link but I'd work with dilfridge to make sure it doesn't break any of the stage builds.  
[18:50:42]  <willikins> https://bugs.gentoo.org/830214 "sys-libs/musl-1.2.2-r7 QA Notice: Found an absolute symlink in a library directory"; Gentoo Linux, Current packages; CONF; ago:blueness

[Comment 5 Sam James 2024-01-01 02:12:00 UTC]

commit a4957cb794dce725b4801ee16a36f38526bdce2d
Author: Sam James <[e-mail]>
Date:   Wed Nov 10 03:31:26 2021 +0000

    sys-libs/musl: create relative symlink to libc.so if existing one fails

    The build system seems to create an absolute symlink to libc.so on
    the host which may not exist.

    If it doesn't (to avoid being disruptive, we could do this unconditionally),
    create a new one relative within ${D} to facilitate SYSROOT installs.

    I've hit this a few times when using crossdev but finally dug into it
    a bit more.

    Bug: https://bugs.gentoo.org/732482
    Signed-off-by: Sam James <[e-mail]>