-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orion/E userland #8
Comments
Moved the old |
On PowerPC, we get this, when trying to do a
|
It seems that we didn't have all of the userland, since we pulled it from an older Orion master, so I've synced-it-up, in the last commit. |
On PowerPC, we can reproduce this error (same as vmlemon/Orion#26), after pulling everything in, and rebuilding the userland:
|
We still get:
The versions are very similar: vmlemon/Orion#26 (comment) |
After synchronising with the master branch of Orion, all of the Orion userland seems to build, and link without problems, on x86-64. |
Orion/E doesn't really help with the PowerPC problems, other than diagnosing what's intrinsically broken, in upstream Pistachio, and what's newly-broken, by merging in the NICTA fork, but it does at least get us closer to having some kind of solution to vmlemon/Orion#3... |
The current Enryo userland used to build, fine, on x86-64 (and, probably still does), but doesn't seem to compile on PowerPC, and contains a different set of components, and functionality, which works to an extent, but is quite hacky, and broken.
This issue proposes to port the Orion userland, as an interim measure, to create the Orion/E (for "Enryo", and "(Community) Enhancements") product, until we can fix up Orion's converged kernel, to properly work on x86, again.
The text was updated successfully, but these errors were encountered: