Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ptsfa!ihnp4!cbosgd!cblpf!cbstr1!Karl.Kleinpaste
From: Karl.Kleinpaste@cbstr1.att.com
Newsgroups: comp.emacs
Subject: Re: Getting GNU Emacs up on a 3B2
Message-ID: <337@cbstr1.att.com>
Date: Fri, 21-Aug-87 10:21:49 EDT
Article-I.D.: cbstr1.337
Posted: Fri Aug 21 10:21:49 1987
Date-Received: Sun, 23-Aug-87 04:50:31 EDT
References: <683@julian.UWO.CDN> <6833@steinmetz.steinmetz.UUCP>
Sender: karl@cbstr1.att.com
Lines: 17

In article <332@cbstr1.att.com> I can't believe I wrote:
   [b] If your binary is trying to be 1.5Mb long, you probably have -O
   optimization turned on.  Check your ymakefile and change
   C_DEBUG_SWITCH to C_OPTIMIZE_SWITCH.  (That's something of a misnomer
   in the case of 3B{2,5,15}'s, because the optimizer is broken; but
   C_OPTIMIZE_SWITCH at least turns the -O switch off.)

Erph, boy, must have been a long night just before typing that.
Obviously, I meant that a binary trying to be 1.5Mb long means that
the -g debugger-info option was on.  Use of -O would turn on
optimization and would reduce the size of the resulting binary.  But
the problem is that the 3B{2,5,15} optimizer is broken, and one should
simply turn both -g and -O off; for the 3B{2,5,15}, one does this with
C_OPTIMIZE_SWITCH, which has a null expansion.  Jeesh.  Sorry.

Egg on my face and all that rot,
Karl