893932 – sys-apps/busybox[static] doesnt depend on sys-libs/llvm-libunwind[static-libs] in llvm musl system

Bug 893932 - sys-apps/busybox[static] doesnt depend on sys-libs/llvm-libunwind[static-libs] in llvm musl system

Summary: sys-apps/busybox[static] doesnt depend on sys-libs/llvm-libunwind[static-libs...

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Embedded Gentoo Team

URL:
Whiteboard:
Keywords:

Depends on:	892956
Blocks:
	Show dependency tree

Reported:	2023-02-11 08:44 UTC by Librecat
Modified:	2023-03-03 22:23 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
emerge --info (file_893932.txt,16.99 KB, text/plain) 2023-02-11 08:44 UTC, Librecat	Details
busybox build log (build.log,481.66 KB, application/octet-stream) 2023-02-11 08:52 UTC, Librecat	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Librecat 2023-02-11 08:44:40 UTC

Created attachment 850372 [details]
emerge --info

enabling static-libs on llvm-libunwind fixed the build failure with static and the build also didnt fail without the static use flag

Comment 1 Librecat 2023-02-11 08:45:40 UTC

-flto=thin was disabled for busybox with package.env but didnt result in any changes

Comment 2 Librecat 2023-02-11 08:52:51 UTC

Created attachment 850374 [details]
busybox build log

Comment 3 Librecat 2023-02-11 09:51:30 UTC

steps to reproduce after stage3 unpack
1 - emerge-webrsync
2 - add -pam and static useflags to sys-apps/busybox
3 - emerge busybox
4 - fails

Comment 4 Librecat 2023-02-11 10:11:07 UTC

forgot to say stricter use flag on clang was enabled

Comment 5 immolo 2023-02-16 23:20:03 UTC

I hit this today also but with strict off being the only difference.

Comment 6 Sam James archtester

2023-03-03 22:23:08 UTC

I've fixed bug 892956 so this should be sorted now.