building unpatched glibc from scratch

[Arnd-Hendrik Mathias <arnd-hendrik dot mathias at nefkom dot net>]

Hi,
I am trying to build the GNU toolchain from scratch and (once again) 
facing a common problem: There seems to be a cyclic dependency between 
glibc and gcc in the following way:

Without glibc (especially the start files crti.o etc.), gcc can only be 
built static, which is done as the first step to build glibc. A static 
gcc is built without the libgcc_eh which again is needed to build the 
glibc. To build the libgcc_eh it is necessary to build a dynamic gcc 
which requires at least the crti.o files etc. from the glibc.....

I found quite brief discussions of this problem in various forums 
(especially those of distros dealing with building from scratch like 
lfs, gentoo etc. but also ubuntu and generic linux mail archives) where 
it is generally solved by various patches. However, none of them offers 
a straightforward systematic solution without patching the glibc sources.

I am trying to learn and gain a deeper understanding of building my 
system (and the toolchains for my embedded targets as well). So can 
anyone point me to a documentation of the glibc developers ' base 
concept of building the gnu tools with glibc?
Best regards

A.-H.