RE: problem building toolchain with uclibc

["Amir Tsvitov" <amir dot tsvitov at percello dot com>]

> -----Original Message-----
> From: Yann E. MORIN [mailto:yann.morin.1998@anciens.enib.fr]
> Sent: Thursday, February 12, 2009 9:08 PM
> To: Amir Tsvitov
> Cc: crossgcc@sourceware.org
> Subject: Re: problem building toolchain with uclibc
> 
> Amir,
> All,
> 
> ( Sorry for the previous post, bad key-combo... :-( )
> 
> On Thursday 12 February 2009 13:16:53 Amir Tsvitov wrote:
> > [>>] Attached config files for mipsel using uclibc and glibc. My
> requirement
> > was to use gcc 4.2.0 (no restrictions on other components)
> 
> Thank you. Unfortunately, that will not be of great use, as you are
> using
> your own (customised?) kernel headers. So I won't be able to reproduce
> the
> toolchain, and surely others won't be either.
> 
> Do you have a requirement to use custom kernel headers? Can't you be
> using
> pristine ones?

[>>] honestly I don't know enough to answer this question. I had to
customize the header files to support some [>>] of the features we need.
I didn't know if the changes will affect the toolchain or not so I used
ours 
[>>] instead of the pristine one. I would much rather use the pristine
ones however because it seems like a much [>>] cleaner way to go. Are
there clearly defined rules as to what header changes affect the
toolchain? I will [>>] gladly rebuild the toolchains if you think they
will work.  
[>>] Thanks,
[>>] Amir


> --
>
.-----------------.--------------------.------------------.-------------
-------.
> |  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