libgcc_s?

[Alexandre Oliva]

On Jun  8, 2002, "Howard Chu" <hyc@highlandsun.com> wrote:

> A brief synopsis on how to build a shared library without any dependency on
> libgcc_s.so would be much appreciated

-static-libgcc

> If there's something I can throw into my specs file and forget about, that
> would be helpful, because I don't want to have to change all the Makefiles
> and configure scripts for all the packages I build.

You could presumably tweak the default specs such that you'd have to
use -shared-libgcc to get libgcc_s linked in.

> It's also an item of discomfort for me now, because I'm shipping something
> that I didn't build explicitly, something with which I have no intimate
> familiarity. In contrast, I've read every single line of source code of the
> other items, I built them explicitly and I stand behind their functionality.
> This item's a wildcard, I dunno what's inside, why it's needed, whether my
> bundled version is even right for a customer's platform.

One way or the other, you'll probably have libgcc code linked in, so
it's not like you're getting new code into your applications.
It's just explicit now.

-- 
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                Professional serial bug killer