open this bug as a issue tracker to push forward building embedded system out of prefix environment. will make some input as I go. Now a problem is that we have two offsets, one ${EPREFIX}, the other "/usr/${CHOST}" as specified by ${ROOT}. the ebuild are installed into ${EPREFIX}/usr/${CHOST}/${EPREFIX} (double prefixed) I tried to unset EPREFIX var when doing cross emerge, but portage fails to find its files. So we have a first problem here: portage (or prefix-portage) should distingish the EPREFIX for itself and the EPREFIX for building. of course the zeroth problem is to port crossdev to Prefix ;) Reproducible: Always
All interested... I don't know the status here, and frankly, I don't care. I'm tired of answering glibc questions in IRC "why is it here?" "how can I emerge it?" "what does this compilation failure mean?" - and the questions are on the rise since it was included in the prefix tree (even unkeyworded). Therefore, I have removed the package from the prefix tree. Please continue your work in an overlay and add it back when you have a working solution (with appropriate mask message for normal users).
(In reply to comment #1) > I don't know the status here, and frankly, I don't care. I'm tired of answering > glibc questions in IRC "why is it here?" "how can I emerge it?" "what does this > compilation failure mean?" - and the questions are on the rise since it was > included in the prefix tree (even unkeyworded). > > Therefore, I have removed the package from the prefix tree. Please continue > your work in an overlay and add it back when you have a working solution (with > appropriate mask message for normal users). Okay, I have no objection for this action.
If cross-merging is still something that's desirable, someone needs to restart those efforts.
