Re: Generating a toolchain for big-endian arm with ct-ng.

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Gilles, Mike,
All,

On Tuesday 06 January 2009 14:33:29 Gilles Chanteperdrix wrote:
> a toolchain based on gcc 4.3.2 and glibc 2.7 builds fine, and generates
> a working root filesystem, but unfortunately has a bug (
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38674
> ).

So there is no patch yet... Could you ping back here once there's one?

> a toolchain based on gcc 4.2.4 builds fine too, but generates a non
> working root filesytem. It appears that the gcc patch (for gcc 4.2.x)
> for big-endian arm (240-arm-bigendian.patch) lacks the change attached
> to this mail as 240-arm-bigendian2.patch.

I'll add that as 241-arm-bigendian2.patch to be sure of the patch ordering.

> trying to build the toolchain with an earlier version of glibc fails,
> glibc is looking for asm/procinfo.h which is not installed by Linux'
> headers_install target.
[--SNIP--]

As Mike pointed out, the patch you later pointed to will be the way to go.
Will add it.

> trying to build a toolchain based on gcc 4.1.2 fails, gcc/tree.h
> includes tree-check.h which can not be found in gcc sources, and seems
> to be required. I did not try to fix this, but thought you might be
> interested.

Well, gcc-4.1.2 is now /old/ and unless there's a patch for it, I won't try
to fix. I'd rather spend my rather sparse time resources on more up-to-date
versions.

Thank you for the reports!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| --==< ^_^ >==-- `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
`------------------------------^-------^------------------^--------------------'


--
For unsubscribe information see http://sourceware.org/lists.html#faq