Summary: | Cannot compile alsa-lib-1.0.10-rc3 in a ulibc based system | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Filippo Sallemi <tonyputi> |
Component: | [OLD] Unspecified | Assignee: | Embedded Gentoo Team <embedded> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | alsa-bugs, tl |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Filippo Sallemi
2005-11-16 07:51:02 UTC
This is matter for who manages uclibc, as I have no clue of if that can be fixed and how. You need to enable USE=wordexp in uclibc if you plan on using alsa. --- From the ebuild --- # uncomment if you miss wordexp (alsa-lib) use wordexp && sed -i -e "s:# UCLIBC_HAS_WORDEXP is not set:UCLIBC_HAS_WORDEXP=y:" .config --- The use flag description --- quse -D wordexp local:wordexp:sys-libs/uclibc: add support for word expansion (wordexp.h) The wordexp function makes uclibc quite a bit bigger in size and it's pretty much only needed by alsa-lib, which is why it's not enabled per default. *** Bug 246704 has been marked as a duplicate of this bug. *** Just so people know, since quite a while you can disable plugins on a per-plugin basis, so you could actually just disable the ladspa plugin on uclibc. On the other hand, the alsa-lib ebuild could add a specific USE-based dep _for just that plugin_ on wordexp when the glibc is uclibc. Up to the ALSA team now though. |