Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!cblpf!cbstr1!Karl.Kleinpaste From: Karl.Kleinpaste@cbstr1.UUCP Newsgroups: comp.emacs Subject: Re: Unexec of GNU on SYS V Message-ID: <295@cbstr1.att.com> Date: Sun, 12-Jul-87 23:15:06 EDT Article-I.D.: cbstr1.295 Posted: Sun Jul 12 23:15:06 1987 Date-Received: Mon, 13-Jul-87 05:47:49 EDT References: <756@gsi2.UUCP> Sender: karl@cbstr1.att.com Lines: 52 Summary: Please be specific about your troubles In-reply-to: alan@gsi2.UUCP's message of 7 Jul 87 15:05:58 GMT Posting-Front-End: GNU Emacs 18.47.3 of Sat Jun 20 1987 on cbstr1 (usg-unix-v) Oh, BY THE WAY... alan@gsi2.UUCP writes: GNU seems to work fine on a Plexus (a 68020 based SYS V box), except for unexec, is there anyone who has any hints which might be causing it to bomb out? *Which* GNU? *Which* Plexus box? *Which* revision of the OS? *Which* system configuration, if it might possibly be significant? For crying out loud, I keep pretty up-to-date on SysVisms of GNU Emacs, and I tend to get a lot of mail from people who've noticed that fact, asking questions about this SysVish OS and that 3B processor. (And RLK handles questions about X peculiarities, and bob@osu-eddie or I get questions about UUCPing GNU things from osu-eddie, and I don't know who handles most ordinary BSD questions...) Last week, I got mail from someone who asked me some generic question about why GNU Emacs wouldn't build on his SysV VAX. After about 4 messages back and forth, lo and behold, the bozo was in possession of (gag) GNU Emacs 16.something. Let's just say that 16.anything didn't have a snowball's chance of ever really running on a SysV box of any flavor. If you're going to ask questions of the whole blasted planet, would you PLEASEPRETTYPLEASE... [a] Tell us *exactly* which version of GNU Emacs you've got. Don't say "18.xx," because the "xx" matters one heck of a lot if you're on a 3B processor, as a case in point. [b] Tell us *exactly* which processor you're using. "VAX" is not necessarily sufficient; MicroVAXen have been known to have problems not found in an 11/780. "3B" isn't sufficient, either; a 3B15 is completely different from a 3B20. [c] Tell us *exactly* which operating system you've got. Just saying that you've got "a VAX" is hardly sufficient, since that doesn't even tell us if you're running 4BSD or SysV. "VAX running BSD" isn't sufficient, either, since you might be running (e.g.) 4.1BSD, which is going to require an answer quite different from 4.3BSD. Similarly for SysV.0 versus SysV.2. [d] Tell us anything that might possibly be odd about your particular situation, especially if it's on a system/OS combination which is supposed to be readily supported. Do you have a newer C compiler than the generic one which your configuration would normally have? Is your SysV not *quite* SysV (e.g., has Berkeley IPC been grafted into it?)? Did your vendor supply an unusual signal library? Sorry to be appearing (in all probability) quite flammable; it's not really intended that way. But trying to answer questions without knowing the whole situation can be mighty frustrating. Cheers, Karl