Subject: libgcc & PIC
To: None <>
From: Hubert Feyrer <>
List: tech-toolchain
Date: 04/29/1999 12:00:31

I've stumbled across this on Solaris, but I think that the same applies
for NetBSD: If I compile some C source where egcs decides to place some
calls to libgcc.a, this works fine if I build an executable file.

But what if I want to build a shared library or some shared object (like,
say, for an Apache DSO)? The DSO will contain and require PIC code, but
libgcc.a can't offer that, which resulted in runtime linker errors on
Solaris for me.

Am I missing something very obvious here, or is this really a flaw in
egcs? (Which I just can't believe, really!)

 - Hubert

NetBSD - better for your uptime than Viagra