On Wed, Sep 27, 2006 at 08:22:14AM -0500, george r smith wrote: > A friend has asked me if someone on the lists I receive can answer the > following: > > "gcc can't find libgcc.a, even though I can find it." > > We are not c programmers and really have no clue.
There's not really enough information here to solve the problem. It's generally not necessary to explicitly add -lgcc to the link line, unless you're invoking the linker directly. In some cases, gcc may link with a dynamic libgcc rather than the static one, so it's possible that you're missing the dynamic one for some reason. It's also possible that you're running up against some 32/64-bit naming problems. There are really a wide range of possibilities here. To understand what's happening, it will be necessary to see the command lines that are being invoked and what gcc is doing with them. The best way to do this is to add -v to the command line, then send both the command line and its output. -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!" _______________________________________________ opensolaris-help mailing list [email protected]
