[OpenBIOS] Some encountered issues when compiling openbios on a ppc64 host

Stefan Reinauer stepan at openbios.org
Tue Jan 19 21:59:34 CET 2010

On 1/19/10 8:00 PM, Blue Swirl wrote:
>> But frankly, the better solution would be to drop our libgcc copy and use
>> that of gcc again... It was a design mistake to let our own copy sneak in.
> I disagree. Having our own libgcc makes OpenBIOS independent of any
> installed libc headers of the host. 
libgcc and libc headers have nothing to do with each other. libgcc is
part of gcc, and any gcc without libgcc is to be considered an
incomplete toolchain.
> You can also use target-elf/-eabi
> cross-compilers, which are easier to build than for example
> target-linux. 
Yes, but if those are built correctly, they still come with libgcc. If
they don't, it makes more sense to file a bug report with the toolchain
provider than to duplicate parts of the toolchain in openbios.
> At least for Sparc32/64, the administrative burden has
> not been very big, though I don't know about PPC.
The administrative burden is higher than using a complete toolchain...
Who is supplying gcc without libgcc anyways?
> This is the same approach as taken by Linux.
Not a very good argument. libgcc is part of gcc. So there is no reason
to duplicate it in any project. This is not some OS dependency like
crt0.o but very gcc intrinsic.


More information about the OpenBIOS mailing list