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
>
Sorry to but in here, however I've been building the armv5teb (IXP4xx
chip) like this for months. Unfortunately, it's with open embedded (OE).
Not only that, but I've natively built the following with the tools
generated:
Linux 2.6.11.2
Apache 2.0.5
Perl 5.8.7 ran make test Failed 1 test script out of 878, 99.89%
okay which is a known coreutils bug
Python 2.4.1 make test 244 OK 3 tests failed: test_mimetools
test_random test_urllib2
OE is pretty libc neutral so this can usually be done for both glibc and
uClibc.
The hardened and PIE parts are missing from OE. Also the package are
constantly changing and some packages build but don't work. It's a lot
of chaos. And there are not nearly the number of packages as in Gentoo.
Hopefully in the not to distant future will I'll have everything
required to a stage1 build straight from the target. We may have
everything now, but the finishing touches are being done to the native
development environment. Currently, OE and the nslu2-linux project are
in the middle of the SCM switch from BK to something else. Things are
in flux right now and this squares the chaos. I'm sure it'll die down in
a couple weeks.
See
http://www.nslu2-linux.org/wiki/HowTo/OpenSlugNativeCompileEnvironment.
The following for all the packages that are cross built
http://www.nslu2-linux.org/wiki/HowTo/OpenSlugDevInst
Best Regards,
Tommy B.
[g2]
--
[email protected] mailing list
