Re: toolchain compiling questions

[Philippe De Swert <philippe dot deswert at student dot denayer dot wenk dot be>]

Thanks for the answer

But I want to clear up some things.

Quoting Kai Ruottu <karuottu@mbnet.fi>:
 
>  Let's assume you made a steel hammer from scratch, raw timber and a block
> of
> steel and used stone hammer(s), fire etc. to produce it... Now you want to
> replace
> it with a new steel hammer but don't want to use the already made hammer but
> throw it away... Where is the sanity in this?

I'm doing my master thesis on GNu/Linux on embedded systems, so I have to
understand fully what happens when I build a toolchain, and how the different
components interact. I also want to make a debian source package from the
sources, with a script that compiles the whole toolchain.

Therfore, as testing purpose I compiled one with Dan's crosstool, and used the
source (from whixh I knew they would build a working toolchain to minimise
time-loss) to build a new one. That's where I ran into the described problem. I
even used a modified version of the crosstool.sh script from Dan and still it
would not work. 

And I did my homework :-)
I knew about the following steps..problem is, I have to keep the
--disable-shared flag, or else Glibc would not build.

>  Building Linux-targeted toolchain totally from scratch (bootstraping) should
> happen like:
> 
>  1. build binutils
>  2. build GCC using '--disable-shared' and with the Linux-headers only.
> Getting the
>     Linux target headers SHOULD succeed and if one asks this from the
> GCC-gurus,
>     it succeeds at least for them, the gcc-patches had just a discussion
> about this...
>  3. build glibc using the produced GCC
>  4. build GCC again using the produced glibc
> 
>  If you already have glibc produced, there is your steel hammer and the steps
> 1,  4
> and 3 in this order are used later to update binutils, GCC and glibc...
> 
>  The bootstrap-stage happens only once and one can update the toolchain tens
> of
> times later, never starting totally from scratch again.
> 
>  The previous steps are the ones done manually and you should report all
> problems
> with them to gcc-bug so that the GCC-developers (with their steel hammers
> produced years ago) are aware of them... Sometimes some people always produce
>their first happers and also this should succeed.
> 

So if I understand you correctly, once I have a full glibc, I don't have to
recompile it when i change of binutils and gcc version? And what if I want to
use another C-library on my target??

greets,

Philippe

| Philippe De Swert -GNU/linux - uClinux freak-    
|    
| "GNU is the way"     
| 
| Please do not send me documents in a closed format. (*.doc,*.xls,*.ppt)  
| Use the open alternatives. (*.pdf,*.ps,*.html,*.txt)  
| Why? http://pallieter.is-a-geek.org:7832/~johan/word/english/  


--------------------------------------------------------------------------
Gestuurd via het webmailsysteem van het De Nayer Instituut: www.denayer.be


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com