home *** CD-ROM | disk | FTP | other *** search
- x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Fri, 20 Nov 1992 14:24:44 EST
- Return-Path: bha <@ada3.ca.boeing.com:bha@gumby>
- Date: Fri, 20 Nov 1992 11:21:14 PST
- From: @lucid.com,@ada3.ca.boeing.com:bha@gumby.boeing.com (bha)
- Subject: Building 19.3 on Sun Sparc
- Message-ID: <9211201921.AA05127@gumby.ata>
- X-Envelope-To: jwz@lucid.com, help-lucid-emacs@lucid.com
- Newsgroups: alt.lucid-emacs.help
- Path: sparky!uunet!wendy-fate.uu.net!help-lucid-emacs
- Sender: help-lucid-emacs-request@lucid.com
- Lines: 22
-
- > Date: Fri, 20 Nov 92 10:48:43 PST
- > X-Windows: Japan's secret weapon.
- > From: Jamie Zawinski <jwz@lucid.com>
- > Sender: jwz%thalidomide@lucid.com
- > References: <9211191739.AA03672@gumby.ata>
- >
- > I think this happens when the malloc(0) returns NULL but the X libraries are
- > not compiled with the flag that tells them that this happens. Why they need
- > a compile-time flag for this instead of just *dealing* with it, I don't know.
- > Good solution: recompile your X libraries with this flag.
-
- Not possible as they are the ones that come from Sun in the
- OpenWindows2 distribution. I don't want to get into multiple versions
- of the X libraries and all that...
-
- > Not so good
- > solution: modify gmalloc.c to actually allocate memory for 0-length blocks.
- > Worse solution: use the system malloc.
-
- Hasn't anyone else had this problem?
-
- ba
-