Summary: | recognize *-linux CHOST without -gnu in qt.ebuild files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Olaf Hering <gentoo> |
Component: | [OLD] KDE | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flameeyes |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Olaf Hering
2006-04-02 08:41:53 UTC
Are you sure that CHOST definition is valid? All the CHOST checks for linux waits for the fourth part, that's -gnu for glibc and -uclibc for uclibc based systems... I'm not 100% sure, but I do know that all major distros have arch-vendor-linux since forever. No they don't, they use arch-vendor-linux-gnu, and for what Gentoo is concerned, only 4-parts CHOST are supported. ppc64-yellowdog-linux , powerpc64-suse-linux. they certainly do. reassign it to the docu or whatever team to make the comments in make.conf more than clear about the chost content. so how exactly is this ppc64 specific? i386-redhat-linux , i486-linux-gnu (on some debian box) someone has to reassign it back to qt@gentoo.org ok, I added this change to qt-3.3.6 |