Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!sri-spam!mordor!lll-tis!ptsfa!hoptoad!academ!uhnix1!nuchat!steve From: steve@nuchat.UUCP (Steve Nuchia) Newsgroups: comp.unix.xenix Subject: Re: Getting Emacs and Elm running on Microport. Message-ID: <253@nuchat.UUCP> Date: Sat, 11-Jul-87 01:23:06 EDT Article-I.D.: nuchat.253 Posted: Sat Jul 11 01:23:06 1987 Date-Received: Fri, 17-Jul-87 06:18:25 EDT References: <151@qetzal.UUCP> <223@Mannix.iros1.UUCP> Organization: Public Access - Houston, Tx Lines: 29 Keywords: Portability, help Summary: make sometimes hoses ld In article <223@Mannix.iros1.UUCP>, fortin@iros1.UUCP (Denis Fortin) writes: > Microport 2.2 system. Somehow, in both cases, the "ld" program just > hangs (after I have been able to compile everything successfully). > I suspect that this is due to a lack of RAM (I have only 1MB), > but I would like confirmation before I go out and buy more memory! Having only one meg with microport can make ls seem to hang :-( I found it barely usable with one meg, but it is entirely acceptable with 5 meg, and in fact 2 meg is plenty for most uses. I never swap, no matter what, with 5 meg; clearly overkill. In several of the packages I'v ported to the beastie I've found that make was botching the call to ld, usually passing a blank or null argument. It doesn't show up on the screen, of course, making it tricky to diagnose. Haven't seen the loader just plain lock up, though. recomended diagnosis procedure: run make -n > file so you've got the text to work with. Now copy the ld command into another file and cut it in half, lopping off the right-hand half or so. run it. It should run to completion and complain about missing symbols. If so, the problem is in the right half. If it locks up, the problem is in the left half. etc. If the command runs ala "make -n | sh" the problem is in make's command invocation. Look for macros with null expansions in the command line. Hope this is of some use to someone. Steve Nuchia