explanation for variables passed to glibc's configure in ch5 inadequate

[ken@…]

With the "new build method", we pass

libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes

and then for the first of these we say

libc_cv_forced_unwind=yes
The build requires support for forced unwind, but because 
it is being cross compiled, it cannot auto detect it. 
Setting this variable on the command line explicitly tells 
the configure script that support is available.

We certainly need to pass this variable, but the explanation is simplistic. Sure, configure and config.log will report that TLS support is required, but if you look in config.log what is actually happening is that the cross-ld program cannot be used because it can't (yet) find crt1.o (which will installed by glibc).

So, I think our explanation (configure cannot auto-detect this) is misleading and sidesteps the real issue (ld doesn't work until crt1.o is in place).

[bdubbs@…]

How about changing the first sentence to:

Because Glibc is being cross compiled and crt1.o is not yet in place, support for forced unwind cannot be autodetected.