The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Architecture proposals/CoreToolchainSplit
From Mer Wiki
(Difference between revisions)
(New page: = Introduction = I'm thinking of a split of Mer into two OBS projects. * Mer into a smaller Core (which doesn't have to be self-hosting) * Mer Toolchain (is self-hosting, doesn't need t...) |
(→cross-gcc-bootstrap) |
||
| Line 24: | Line 24: | ||
== cross-gcc-bootstrap == | == cross-gcc-bootstrap == | ||
| − | This will construct a bootstrap gcc, just enough to build glibc. | + | This will construct a bootstrap gcc, just enough to build glibc. This depends on cross-kernel-headers-TARGET |
* creates cross-TARGET-gcc-bootstrap for X86 (stored in /opt/cross/TARGET/) | * creates cross-TARGET-gcc-bootstrap for X86 (stored in /opt/cross/TARGET/) | ||
Revision as of 17:54, 16 December 2011
Contents |
Introduction
I'm thinking of a split of Mer into two OBS projects.
- Mer into a smaller Core (which doesn't have to be self-hosting)
- Mer Toolchain (is self-hosting, doesn't need to be fully bootable on a
machine, but X86-only).
Toolchain would effectively be able to create all the elements for the pieces in Mer Core for any target, such as bootstrapping the glibc/gcc from X86 side into ARM side and not like we have now, where glibc effectively gets injected from ARM side for a cross compiler to be made.
Packages involved
cross-kernel-headers
This will build kernel headers utilizing for the target.
- creates cross-TARGET-kernel-headers package for x86 (stored in /opt/cross/TARGET/sys-root/)
- creates kernel-headers-TARGET, exported to the target RPM architecture in /
cross-gcc-bootstrap
This will construct a bootstrap gcc, just enough to build glibc. This depends on cross-kernel-headers-TARGET
- creates cross-TARGET-gcc-bootstrap for X86 (stored in /opt/cross/TARGET/)
