| 1 |
On 01/09/2013 12:40 AM, justin wrote: |
| 2 |
> My question, did anybody else might have observed similar things? Is |
| 3 |
> there a flaw in this *ECLASS_ONCE_* stuff? |
| 4 |
|
| 5 |
There could well be, but even in the absence of the *ECLASS_ONCE_* |
| 6 |
stuff, the problem that you're describing could be attributed to eclass |
| 7 |
conflicts that cause order of inheritance to make a difference. For |
| 8 |
example, it could be that multilib.eclass definitions conflict with one |
| 9 |
or more other eclasses, as noted here: |
| 10 |
|
| 11 |
https://bugs.gentoo.org/show_bug.cgi?id=450988#c1 |
| 12 |
-- |
| 13 |
Thanks, |
| 14 |
Zac |
Archives