That worked, thanks Brian and Google :) So the dependency on libgcc_s.so.1 is not necessary and will be removed from the imported interfaces table.
Laca On Tue, 2008-08-26 at 22:26 +0100, Brian Ruthven - Solaris Network Sustaining - Sun UK wrote: > Can't it be eliminated with something like -s?tatic-libgcc ? At least > that's what Google tells me I can do :-) > Or is it specifically required that the libgcc_s library is external > (i.e. dynamically loaded) rather than statically linked in at compile time? > > Brian > > Laszlo (Laca) Peter wrote: > > On Fri, 2008-08-22 at 17:17 -0700, Danek Duvall wrote: > > > >>> 2.2 Imported Interfaces > >>> > >>> Interface Classification Comments > >>> ----------------------------- -------------- ---------------------- > >>> libgcc_s.so.1 Volatile PSARC/2004/742 > >>> > >> Couldn't this be eliminated by using the Studio compiler? > >> > > > > It would, but libffi contains ASM code that doesn't build with > > Sun Studio. It may be possible to build it with a future > > version of Sun Studio. > > ? > > > >> Or does Python require gcc? > >> > > > > No. > > > > Laca > > > >
