Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 593030

Summary: www-client/firefox-49.0_beta8 fails to build on musl-amd64 with 'pthread_setname_np was not declared in this scope'
Product: Gentoo Linux Reporter: tt_1 <herrtimson>
Component: OverlaysAssignee: Gentoo musl team <musl>
Severity: normal CC: blueness, felix.janda, gentoo, mozilla, tsmksubc
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 430702    
Attachments: compressed build.log
patch for sys-libs/musl

Description tt_1 2016-09-07 08:30:17 UTC
Created attachment 445130 [details]
compressed build.log

pthread_setname_np and musl don't seem to like each other?
Comment 1 tt_1 2016-09-07 08:33:19 UTC
Created attachment 445132 [details]
Comment 2 Felix Janda 2016-09-07 11:37:28 UTC
musl doesn't have pthread_setname_np. "np" stands for non-portable, and
indeed for different systems the number and type of arguments differs.
To make firefox happy, musl would need to implement the same variant as
glibc or Mac OSX. In

the musl author says that there are no major objections to adding it.
Comment 3 Felix Janda 2016-09-14 01:54:09 UTC
Created attachment 445634 [details, diff]
patch for sys-libs/musl
Comment 4 tt_1 2016-09-16 18:56:05 UTC
The patch for musl solves the compile error of firefox. Is it a copy from glibc?
Comment 5 Felix Janda 2016-09-17 01:08:30 UTC
No, the function is written from scratch using the man page. An
improved version of this patch is currently being reviewed on the musl
mailing list.
Comment 6 Nicholas Fish 2016-09-17 15:43:40 UTC
I was also able to build and run www-client/firefox-49.0_beta10 against  musl-1.1.15 with the improved version of Felix's patch from .
Comment 7 Ian Stakenvicius (RETIRED) gentoo-dev 2016-09-21 14:27:07 UTC
So if musl is what needs the patch, is there anything I should do before I commit firefox-49.0 to the tree?
Comment 8 tt_1 2016-10-20 08:30:16 UTC
The patch has been commited upstream at
Comment 9 tt_1 2017-01-13 21:21:35 UTC
this has been fixed in musl-1.1.16