home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!spool.mu.edu!uwm.edu!linac!att!cbnewsi!cbnewsh!att-out!cbfsb!cbnewsg.cb.att.com!wto
- From: wto@cbnewsg.cb.att.com (William T. O Connell)
- Subject: Re: How many SLS binaries don't work with new libc.so.4.2?
- Message-ID: <1993Jan4.052116.10447@cbfsb.cb.att.com>
- Summary: known binaries
- Sender: news@cbfsb.cb.att.com
- Organization: AT&T
- References: <1774@emoryu1.cc.emory.edu>
- Date: Mon, 4 Jan 1993 05:21:16 GMT
- Lines: 24
-
- In article <1774@emoryu1.cc.emory.edu>, splee@pd.org (Seng-Poh Lee, Speedy) writes:
- > As part of trying to get uucp running again, I installed libc.so.4.2.
- > Howvever, I'm finding out that a few binaries, such as login (!) don't
- > function under the new shared library (complains about a few undefined
- > library calls). Login was a big one, since once you link in the new
- > shared library, you can't log in anymore! I went back to 4.1 until I can
- > fix and recompile login, but I'm just wondering how many more binaries
- > need to be recompiled. I started out with SLS 0.98p5 distribution but
- > am running the .99p2 kernel now.
-
- The only binaries that I ran across are login and passwd. Though
- there are many that I haven't tested.
-
- Until you get the new source to recompiling them, there is a quick
- work around that work's like a charm. Thus, allowing you to keep
- the 4.2 library.
-
- 1) create symlink on libc.so.4.1 to libc.so.0
- 2) edit login (and any others that you are having problems with)
- with emacs. Search for libc.so.4 using ctrl-s. Change the 4 to a 0.
- 3) Problems fixed. The binary will now use the original shared library
- that it was compiled with.
-
- - Bill O'Connell wto@ihlpx.att.com
-