FW: GCC Cross Compiler for cygwin

[Kai Ruottu]

Amir Fuhrmann kirjoitti:

>1. If I am ONLY interested in the compiler, and do NOT want to build
>libraries, what would be the process ??
>
>  
>
 Be happy with what you already have?

Ok....

 -  'make all-gcc' builds ONLY GCC....

 -  'make install-gcc' installs ONLY GCC

The "ONLY GCC" of course means the stuff built from the 'gcc' 
subdirectory sources... Before the
gcc-2.9 the GCC sources had only the GCC sources, now they include also 
'libiberty' and 'libstdc++'
and some other 'extra' packages...   GCC is only a compiler collection, 
but the 'libgcc*' stuff still being
produced using the GCC for the selected target (usually the just built 
one).  Projects like the Berkeley
Nachos have had instructions for "How to build a naked-GCC, without any 
libraries for the target
system", generally anyone who can use 'touch' or something for creating 
'libgcc.a's, 'libgcc_s.so*'s
etc. "stubs" from scratch, and so get 'make' happy, can build a 
"naked-GCC"...

>2. I looked at newlib, but wasn't sure of the process of including it as
>a combined tree .. Which subdir should I move over to the gcc tree ??
>  
>
 The 'newlib' (the generic C library) and 'libgloss'  (glue libraries 
for target boards)....

 This is another way to build the C library, but sometimes like when 
using an experimental and unstable
GCC snapshot, building the C library with the new GCC can be a little 
questionable....

 Generally the binutils, GCC and the C library builds should not have 
much to do with each others, if one
needs newer or older binutils, one builds them, if a newer GCC then one 
builds that, and if wanting to
rebuild the C library with a better GCC then doing that is highly 
motivated....  But companies like MS
have got people to buy their product again although one already having 
it, the same idea followed with
free software means that one must rebuild what one already has,  "the 
goal isn't important, the continuous
rebuilding is...".  I cannot understand why a separately (or with a PC) 
bought Win2k couldn't be moved
into a new PC after replacing it with Linux, just like moving a 
separately (or with a PC) bought hard disk
People think that  it is not allowed just as that they must build 
everything again when building for a new
host....

 I used to build everything for both Linux and Windoze hosts, Windoze 
being the secondary host and
therefore never requiring rebuilding 'libiberty' and 'libstdc++' or the 
C library...  Only new binutils and
GCC for Windoze host  (and also GDB/Insight but this wan't seemingly  
required by Amir) after having
everything already for the Linux host.  So the 'make all-gcc' was very 
familiar command in those builds
for the secondary host .

 "If At Last You Do Succeed, Never Try Again" (Robert A.Heinlein) is the 
rule after the first "bootstrap"
phase...