Kumba wrote: > Brian Koropoff wrote: > >> As far as I know, crossdev only builds a cross compiler which runs on >> your build system but generates executables for another >> processor/architecture. I've already used crossdev sucessfully to >> generate such a compiler for arm. What I want to do now is build a >> compiler that *runs* on arm and creates arm executables (that is, both >> the host and target platform is arm, not just the target). This should >> be as simple as using portage with my crossdev-built cross-compiler and >> emerging it, but the build fails. Is there any trick to getting portage >> to build a native gcc to be included in the arm root fs? > > > If I'm reading this right, then what you want to do is impossible. > You can't build a gcc that runs on arm, and builds for arm, on a > cross-host. gcc has a rather strange build phase, wherein it rebuilds > itself 2-3 times (if you watch a gcc build closely, you'll see an > "xgcc" and references to stage1 and stage2 bootstraps). As such, if > you want to build a native compiler, you have to build on the native > architecture. This is because when the initial bootstrap completes, > and gcc kicks off it's stage1 xgcc run, that xgcc is an arm binary, > and it tries to build a stage2 xgcc arm binary. If performed on a > fast x86 box, this will fail. > > > --Kumba > Are you sure it's impossible? In order to build a compiler on the native architecture, I'll need a compiler that runs on arm to perform the compilation. However, getting a compiler that runs on arm is what I'm trying to do in the first place! The stage tarballs must contain a complete native compiler toolchain so that a gentoo system can be bootstrapped and built. I assume the gentoo devs are building stage tarballs for arm entirely with portage on a fast x86 build machine. I'm wondering if there is some trick to it that I'm missing. Please correct me if I'm wrong about this.
-- Brian Koropoff -- [email protected] mailing list
