[coreboot] Now Proposal for cross-compiler Re: Simnow & payloads (Was: something else)
Marc.Karasek at Sun.COM
Wed May 14 16:58:26 CEST 2008
Jordan, Marc, Ron, et all.
I found the problem with building coreboot-v2. It was the binutils. I
believe the seg fault in linking tint/coreinfo is the same issue. I
will try to verify this soon.
I would like to propose that we move to a cross-compile type of
environment. We could use crosstools scripts to build a complete
environment that would go under /opt/crosstools.
This could then be used by buildrom to build with. The advantage is
that everyone will be on the same page in terms of gcc/binutils/glibc
versions and we can have a better control over what tools
are used. It gets us away from any distro/tools dependencies. It will
also let us test new toolchains in a very controlled environment.
Another added bonus with a common set of tools is that third-party
can use this without worrying about toolchain issues.
I have some experience in using cross-compilers from other embedded
projects. I have already setup crosstools with gcc 4.1.0 / binutils
2.16 / glibc 2.3.6 on my system. I could take on the task of modifying
buildrom to use this toolchain instead of the "native" toolchain. I
mailto:marc.karasek at sun.com
Jordan Crouse wrote:
> On 12/05/08 12:58 -0400, Marc Karasek wrote:
>> What is tint??
>> Ok I have been able to build a filo payload. And it did work. I think
>> were the problem lies is in LAB.
>> I am wondering how critical is it to have uclibc or a "common/standard"
>> toolchain for building coreboot/payloads.
>> I have built and maintained cross-compilers before. Nothing with uClibc in
>> it but with glibc.
> We seem to bring it up every time we discuss this, but there is probably a
> reason for it: Should we consider outsourcing bulding the LAB to
> buildroot or some other third-party build system that is more willing to
> build and maintain the toolchains?
>> ron minnich wrote:
>>> I pulled down buildrom to my FC8 32-bit system, and made the tint
>>> payload. It worked first time out. Resizing for the 1M bios -- there
>>> was no resizing to do.
>>> If you're cross-building, however, that might make it fun.
>>> My next payload is Plan 9.
More information about the coreboot