problem in cross compiling newlib

[JulyClyde]

I don't understand what "as a module" means.
If I call newlib's own configure, it's a seperated library, while if I
call the configure in the top level directory, newlib is a module. Am
I right?

Yesterday I run
../newlib-1.14.0/newlib/configure --target=arm-linux
and succeed.
Why?

2006/8/11, DJ Delorie <dj@redhat.com>:
> Newlib as a *module* only knows about $host, but the *toplevel*
> configury, which manages all the modules (libgloss, gcc, gas, gdb,
> libiberty, etc) follows the standard where --target is the target,
> --host is where you run the tools, and --build is the machine running
> configure.
>
> It will rearrange the options when it sub-configures into newlib.
>
> Of course, you could have just tried both and watched what happened.
>


-- 
Ren Xiaolei
Information Engineering University of PLA