Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!texbell!uudell!bigtex!james From: james@bigtex.cactus.org (James Van Artsdalen) Newsgroups: gnu.emacs Subject: Re: Dumping, shared/dynamic libs, and SysVR4 Message-ID: <25719@bigtex.cactus.org> Date: 3 Jan 90 06:00:19 GMT References: Reply-To: james@bigtex.cactus.org (James Van Artsdalen) Distribution: gnu Organization: Institute of Applied Cosmology, Austin TX Lines: 30 In , pinkas@joker.intel.com wrote: > I am currently looking into bringing Emacs up on Sys 5.4. I am doing this too. Has anyone been successful using full job control functionality and BSD signal handling? My "approach" was to configure emacs for BSD 4.3 and try to coerce it to work. I believe that this part of the port is mostly OK now. The biggest problem I am having is that SysVr4 on i386 is that the data space starts up above 0x08000000. Emacs uses the upper eight bits for flags. There are some provisions for this kind of environment (DATA_SEG_BITS?), but some places in emacs still use "if (w) { ..." without masking w. > Unfortunately, neither shared nor dynamic libraries are supported by > Emacs at the current time. I got shared libraries to work with SysVr3 a while back. It's no big deal: modify unexec() to scan the temacs binary and copy all sections to the output file, modifying the ones we want to change. Once I get a temacs that runs, I don't expect undumping to be a major undertaking, although shared libraries may take a while longer. PS. Several people sent mail recently asking for the sysVr3 shared library changes. I'm still trying to get those out. -- James R. Van Artsdalen james@bigtex.cactus.org "Live Free or Die" Dell Computer Co 9505 Arboretum Blvd Austin TX 78759 512-338-8789