| Summary: | fnord uses dietlibc also in a uclibc env | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christian Zoffoli (RETIRED) <xmerlin> |
| Component: | New packages | Assignee: | Embedded Gentoo Team <embedded> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | added uclibc support (don't use dietlibc in a uclibc env) | ||
|
Description
Christian Zoffoli (RETIRED)
2004-10-12 14:30:48 UTC
Created attachment 41639 [details, diff]
added uclibc support (don't use dietlibc in a uclibc env)
Is there some reason why that's a problem in a uClibc environment?
Maybe what you want is the ability to control if you use diet at all under * libc.
If so then would adding IUSE=diet not be more appropriate for this case?
We already have 3-4 local USE flags for diet in misc ebuilds that do the same as
this one. You could just do something like.
src_compile() {
use diet && DIET=diet || DEIT=""
emake DIET="$DIET"
}
fixed in cvs |