This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libgcc problem


On Tue, Dec 17, 2002 at 11:33:49AM -0800, Matt Rhodes wrote:
> I have a question that is being passed on to me by a colleague so I don't have all of the exact 
> details.  But basically we have built an executable with gcc version 3.1.1 on our Red Hat 7.1 
> system.  When one of our customers attempts to run the executable on their Red Hat 7.3 system, 
> they get an error that libgcc.so is missing.  Why would this happen?  Are we not linking correctly?  

The libgcc_s.so file should be installed already on their system.  It's
pretty standard.  They can install it from their RH disks or download an
RPM, or you can give them a copy.

> Do we need to somehow link against the static version of the library when we build?

No, that generally causes Bad Things to happen in C++ programs.


Phil

-- 
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]