Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!agate!ziploc!eps From: eps@toaster.SFSU.EDU (Eric P. Scott) Newsgroups: comp.sys.next Subject: Re: Well... questions about upgrade to 2.0 Message-ID: <1452@toaster.SFSU.EDU> Date: 31 Mar 91 08:13:44 GMT References: <1991Mar31.050505.18795@rice.edu> Reply-To: eps@cs.SFSU.EDU (Eric P. Scott) Organization: San Francisco State University Lines: 262 In article <1991Mar31.050505.18795@rice.edu> dboyes@brazos.rice.edu (David Boyes) writes: >1) Where did /lib/libc.a go? It went away. cc now "always" links against the shared library. This is your punishment for not religiously using -lsys_s under previous releases. :-) > I found a libcs.a in /usr/lib -- is > this just a shared version? Nope. This is is a library of nifty goodies from CMU. NeXT seems to have removed the man pages... I know they were there once (0.9?), since I have code that depends on procedures in it. >2) Has anyone successfully compiled Elm 2.3 for 2.0? Well, I've been using 1.0 binaries, but just for you, I just did. Piece of cake. The rest of this article deals with this question, so if you're not interested, hit `n' now... As of this writing, the current release is 2.3PL11. Apply the patches at the end of this article in the usual manner: From rn, say "| patch -p -N -d DIR", where DIR is your elm source directory. Outside of rn, say "cd DIR; patch -p -N