public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* "libgcc_s.so.1: could not read symbols: Invalid operation" compiling kde 2.2.1  on solaris 8
@ 2001-10-17  5:28 Keith Leng
  0 siblings, 0 replies; only message in thread
From: Keith Leng @ 2001-10-17  5:28 UTC (permalink / raw)
  To: gcc-help

My compilation of kdelibs-2.2.1 failed while installing kdoctools. It
printed a warning about a missing libgcc_s.so.1 and aborted because of
undefined
references to libiconv_open and libiconv_close. I downloaded and installed
libgcc_s.so.1 from sunfreeware.

Now it is aborting with the message below. /usr/local/lib/libgcc_s.so does
exist, it is a symlink to libgcc_s.so.1. Running nm against this library
returns a valid list of symbols. I have gcc-2.95.3 installed.

I think the problem maybe that the downloaded library is for 3.0 and I'm
running
2.95.

Any help would be much appreciated.

Error Message
----------------

Wl,--rpath -Wl,/usr/local/lib:/usr/openwin/lib -Wl,--rpath -Wl,/usr/openwin/
lib
/usr/local/lib/libgcc_s.so.1: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [kio_help.la.closure] Error 1
make[3]: Leaving directory `/usr/local/source/kde/kdelibs-2.2.1/kdoctools'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/source/kde/kdelibs-2.2.1/kdoctools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/source/kde/kdelibs-2.2.1'
make: *** [all-recursive-am] Error 2


$

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2001-10-17  5:28 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-17  5:28 "libgcc_s.so.1: could not read symbols: Invalid operation" compiling kde 2.2.1 on solaris 8 Keith Leng

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).