On 12/22/10 13:03, Somebody in the thread at some point said:
>> I wanted to see how the corss toolchain for fedora was built
>> tried to fetch is source RPMs.
Thanks for the URL.
I tried to build an rpm on Fedora 14 - x86_64 and it doesn't build:
+ /usr/bin/patch -s -p0 -b --suffix .ppc64-m32-m64-multilib-only~
1 out of 1 hunk FAILED -- saving rejects to file gcc/config/rs6000/t-linux64.rej
What happened is that rpmbuild changed since these old cross packages
were built, it enforces --fuzz=0 now when it didn't before. So as you
found, its own patches in the SRPM won't apply.
> CodeSourcery is an ugly tarball approach, I don't know about
> Since cross is only needed for Kernel and Bootloader with the Fedora
> packaging approach, you're best off using the Fedora cross packages and the
> Fedora native toolchain for everything else.
I agree. However, I wanted to know that if we go about providing a
would support ARMv7, then where would we pick the source code from?
I assume that Fedora tool-chain is built from GNUARM.
Please do correct if my assumption is wrong.
CodeSourcery and if I understood it GNUARM are not magic toolchains,
they're just built and maintained versions of standard packages like
binutils and gcc same as Fedora does. The difference is that overall,
Fedora is a consistent distro and these are just tarball blobs.
A few weeks ago I did the work to uplevel the cross patches to what was
then current rawhide gcc and binutils, and posted the specfile patches
and instructions for rebuild to the list (where it disappeared silently
like a stone in a lake deep in a forest ^^):
If you want to recook or uplevel the cross packages, that would be the
place to start.