Chí-Thanh Christopher Nguyễn:
> hasufell schrieb:
>> No improvements so far. I am going to hardmask sys-devel/crossdev,
>> unless someone can explain why we are still in broken stage.
>>
>> More packages are popping up that randomly break. Recent failures were
>> related to tc-getBUILD_CC.
>>
>> This isn't stable in any way. I'm not blaming anyone, but that's what
>> hardmasking is for. A working solution was declined, so...
>
> If I understand correctly, it is not the crossdev package being present on
> the system, but the generated toolchains that cause the trouble.
>
> I think there are less intrusive options than hardmask, such as pkg_pretend()
> check or blocking offending packages from cross-${CTARGET} category.
>
>
> Best regards,
> Chí-Thanh Christopher Nguyễn
>
>
There was a proposed solution which works perfectly fine: don't clutter
PATH with crossdev links.
If any embedded developer needs these tools in PATH he can add them
temporarily (I'm pretty sure he knows how; an elog can be added as
well), via wrapper scripts or whatnot. That's a reasonable trade-off.
However, toolchain does not agree and I don't randomly touch other
peoples packages (unless there is no response).
So there are only two things left:
* block crossdev within multilib eclasses (that sounds really wrong to me)
* hardmask it, so we are able to communicate this problem to the user
