Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!edcastle!dcl-cs!cam-cl!news From: dahe@cl.cam.ac.uk (David Elworthy) Newsgroups: comp.sys.acorn Subject: GhostScript and Shared C Library Message-ID: <1991May14.091627.14770@cl.cam.ac.uk> Date: 14 May 91 09:16:27 GMT References: <1991May13.215823.28893@cbnewse.att.com> Reply-To: dahe@cl.cam.ac.uk (David Elworthy) Organization: U of Cambridge Comp Lab, UK Lines: 28 I said in a posting yesterday that some people had had problems with GhostScript. When they tried to start it, they got "shared C library out of date". This message comes from the C "Stubs" library, which is the interface to the CLib module - it checks that the version of the module loaded is consistent with what it is expecting from it. GhostScript was developed with the (unreleased) version 3.69 of CLib, and the corresponding Stubs. I had a look round my hard discs and backup floppies yesterday, but I've been unable to find an earlier version of Stubs, so I am unable to recompile it to work with CLib 3.50 or 3.66. If anyone wants to do this, there are some points to note. Firstly, the makefile is *not* compatible with the standard Acorn version of make (something I've only just discovered), so if this is all you have, you will have to either fiddle with it, or just compile each source file individually. Look at GLibVia and ILibVia to find the files which form the GLib and ILib libraries (which you make with libfile). Then look at the target line for !RunImage in the makefile to see what else you need to do the overall build. (Off the top of my head, I *think* the files you will need to compile are gs.c, gsmain.c, utrace.c, gp_arc.c, gdevarc.c and the WimpPlus files wimpc.c and wimpio.c, but I would advise you to check this). Finally, I think a change is necessary in gs.c for earlier version of Stubs. In the "main" function, the call to wimpc_init must be moved to before any of the calls to gs_malloc, so the heap is initialised at the right time. I apologise again for the nuisance this has caused. When I upgraded, I simply didn't expect or know that I would need earlier versions of things. -- david elworthy