Error building cross-gcc libgcc_s.so

[Alexandre Oliva]

On Dec 28, 2000, Michael Eager <eager@mvista.com> wrote:

> Since crti.o (or crtn.o) isn't built in the current directory, the 
> linker cannot find it. 

They're supposed to be supplied by the C library.

> Why should crti.o and crtn.o be included in a shared library?

Because otherwise the library won't be properly initialized.

> Or in libgcc?

Likewise.

> Why is libc also linked in with libgcc?

Because libgcc depends on symbols supplied by the C library.

> Since newlib hasn't been built, there isn't one to link with.

You don't want newlib for a GNU/Linux tool-chain.  You want glibc.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me