home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!ukma!darwin.sura.net!rsg1.er.usgs.gov!ornl!jamsun.ic.ornl.gov!mullens
- From: mullens@jamsun.ic.ornl.gov (James A. Mullens)
- Subject: SLS, g++, shared libs, and X
- Message-ID: <1992Nov12.174446.9480@ornl.gov>
- Sender: usenet@ornl.gov (News poster)
- Organization: Oak Ridge National Laboratory
- Date: Thu, 12 Nov 1992 17:44:46 GMT
- Lines: 21
-
- * Newbie alert *
-
- I'm using the "latest-1" distribution of SLS to run some C++/X software
- I wrote for a Sun, and I'm having trouble linking. Linking to shared
- libs would be nice, and I tried it despite words in the documentation
- about X stuff not having jump tables -- it bombs horribly when it runs.
- Linking "static" is acceptable but the linker complains about not finding
- functions usually located in libm. Is the solution just to move the
- correct libm file into the correct directory, or is something else going
- on here?
-
- The documentation touches on these topics, but I'd love to see a summary
- of the relationships between:
- standard libs and shared libs (classic and jump table),
- gcc (vs g++?) libs (libm in particular),
- X libs.
-
- jim mullens
- Internet: jcm@ornl.gov (128.219.128.17)
- mullens@jamsun.ic.ornl.gov (128.219. 64.31)
- Dammit Jim! I'm a program, not a doctor!
-