From xemacs-m  Tue Feb 11 13:03:09 1997
Received: from alphatech.com (erebus.alphatech.com [198.112.236.2])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA24847
	for <xemacs-beta@xemacs.org>; Tue, 11 Feb 1997 13:02:16 -0600 (CST)
Received: from venus.alphatech.com by alphatech.com (4.1/SMI-4.1)
	id AA12471; Tue, 11 Feb 97 13:57:52 EST
Received: from pochacco.alphatech.com by venus.alphatech.com (4.1/SMI-4.1)
	id AA09562; Tue, 11 Feb 97 14:05:29 EST
Received: by pochacco.alphatech.com (SMI-8.6/SMI-SVR4)
	id NAA18130; Tue, 11 Feb 1997 13:56:30 -0500
Date: Tue, 11 Feb 1997 13:56:30 -0500
Message-Id: <199702111856.NAA18130@pochacco.alphatech.com>
From: greg@alphatech.com (Greg Klanderman)
To: xemacs-beta@xemacs.org (XEmacs beta list)
Subject: trouble with 19.15b93 on solaris 2.5
Reply-To: greg@alphatech.com




OK, first I got around the problem I was having with SOCKS by changing
the following line in src/s/sol2.h:

#define LIBS_SYSTEM -lresolv -lsocket -lnsl -lkvm -lelf -lgen -ldl

to add "-lresolv".  Things now build somewhat fine.  First, my
configuration: 


./configure --extra-verbose --prefix /local/mstar/software/xemacs/install \
            --site-includes=/local/mstar/software/install/include \
            --site-libraries=/local/mstar/software/install/lib \
            --with-dialogs=motif --with-menubars=lucid --with-scrollbars=lucid \
            --x-includes=/usr/openwin/include --x-libraries=/usr/openwin/lib \
            --debug --error-checking=none \
            --with-socks --cflags="-g -O2" >& RESULT-CONFIGURE-GREG

gives:

Configured for `sparc-sun-solaris2.5'.

  Where should the build process find the source code?    /local/mstar/software/xemacs/build/xemacs-19.15-b93
  What installation prefix should install use?		  /local/mstar/software/xemacs/install
  What operating system and machine description files should XEmacs use?
        `s/sol2-5.h' and `m/sparc.h'
  What compiler should XEmacs be built with?              gcc -g -O2
  Should XEmacs use the GNU version of malloc?            yes
  Should XEmacs use the relocating allocator for buffers? yes
  What window system should XEmacs use?                   x11
  Where do we find X Windows header files?                /usr/openwin/include
  Where do we find X Windows libraries?                   /usr/openwin/lib
  Additional header files:                                /local/mstar/software/install/include
  Additional libraries:                                   /local/mstar/software/install/lib
  Compiling in support for SOCKS.
  Compiling in support for XAUTH.
  Compiling in support for XPM.
  Compiling in support for X-Face headers.
  Compiling in support for GIF image conversion.
  Compiling in support for JPEG image conversion.
  Compiling in support for PNG image conversion.
  Compiling in native sound support.
  Compiling in support for DBM.
  Compiling in support for SOCKS.
  Using the Lucid menubar.
  Using the Lucid scrollbar.
  Using the Motif dialog boxes.
  Compiling in extra code for debugging.
  Compiling in code for checking XEmacs memory usage.


building (I grabbed a clean distribution, no patching, on a new
filesystem so no old junk around) goes OK, though I get the following
warnings in event-Xt.c:

event-Xt.c: In function `x_to_emacs_keysym_sunos_bug':
event-Xt.c:622: warning: passing arg 1 of `XLookupString' from incompatible pointer type
event-Xt.c:627: warning: `return' with a value, in function returning void
event-Xt.c:634: warning: `return' with a value, in function returning void
event-Xt.c:635: warning: `return' with a value, in function returning void
event-Xt.c:636: warning: `return' with a value, in function returning void
event-Xt.c:637: warning: `return' with a value, in function returning void
event-Xt.c:638: warning: `return' with a value, in function returning void
event-Xt.c:639: warning: `return' with a value, in function returning void
event-Xt.c:640: warning: `return' with a value, in function returning void
event-Xt.c:641: warning: `return' with a value, in function returning void
event-Xt.c:645: warning: passing arg 1 of `XLookupString' from incompatible pointer type
event-Xt.c:648: warning: `return' with a value, in function returning void
event-Xt.c:658: warning: `return' with a value, in function returning void
event-Xt.c:662: warning: `return' with a value, in function returning void
event-Xt.c:681: warning: `return' with a value, in function returning void
event-Xt.c:683: warning: `return' with a value, in function returning void
event-Xt.c: In function `x_event_to_emacs_event':
event-Xt.c:802: warning: passing arg 1 of `x_to_emacs_keysym' from incompatible pointer type
event-Xt.c: In function `quit_char_predicate':
event-Xt.c:2058: warning: passing arg 1 of `x_to_emacs_keysym' from incompatible pointer type

Since the rest of the code compiles without so much as a peep I'm
looking into this and there seems to be a problem here.  It looks like
SUNOS_GCC_L0_BUG is getting defined (not sure where/why yet, but I
tried out that program to check for the GCC bug posted yesterday and
it said things were fine (i'm using 2.7.2)).  The function
x_to_emacs_keysym_sunos_bug() is not properly overriding all "returns"
in that function by #defining return().  Some returns are missing
parens.  More in a later message - I'll look into this further first.

Later, when loading up, I get the doc-string warnings others have had:

Finding pointers to doc strings...
Note: Strange doc (weird function) for function set-face-font @ 851483
Note: Strange doc (weird function) for function set-face-foreground @ 853011
Note: Strange doc (weird function) for function set-face-background @ 854568
Note: Strange doc (duplicate) for bytecode define-widget @ 1150434
Finding pointers to doc strings...done
Warning: doc lost for function font-dropcaps-p.
Warning: doc lost for function custom-facep.
Warning: doc lost for function extent-property.
Warning: doc lost for function font-smallcaps-p.
Warning: doc lost for function font-reverse-p.
Warning: doc lost for function set-font-strikethru-p.
Warning: doc lost for function set-font-linethrough-p.
Warning: doc lost for function set-face-font-family.
Warning: doc lost for function font-original-set-face-background.
Warning: doc lost for function set-font-blink-p.
Warning: doc lost for function set-font-italic-p.
Warning: doc lost for function font-original-set-face-font.
Warning: doc lost for function set-font-underline-p.
Warning: doc lost for function font-italic-p.
Warning: doc lost for function font-oblique-p.
Warning: doc lost for function set-font-dim-p.
Warning: doc lost for function set-face-font-size.
Warning: doc lost for function font-dim-p.
Warning: doc lost for function set-font-bigcaps-p.
Warning: doc lost for function font-overline-p.
Warning: doc lost for function set-font-dropcaps-p.
Warning: doc lost for function font-underline-p.
Warning: doc lost for function font-linethrough-p.
Warning: doc lost for function set-font-reverse-p.
Warning: doc lost for function set-font-bold-p.
Warning: doc lost for function set-font-overline-p.
Warning: doc lost for function font-blink-p.
Warning: doc lost for function describe-display-table.
Warning: doc lost for function font-bigcaps-p.
Warning: doc lost for function font-bold-p.
Warning: doc lost for function set-font-oblique-p.
Warning: doc lost for function font-original-set-face-foreground.
Warning: doc lost for function font-strikethru-p.
Warning: doc lost for function x-color-values.
Warning: doc lost for function set-font-smallcaps-p.

Finally, running xemacs -q assert fails on the second keypress, as
others have noted:

Fatal error: assertion failed, file events.c, line 749, abort()
 
Fatal error (6).

 [:]
 
Lisp backtrace follows:
 
  # (condition-case ... . error)
  # (catch top-level ...)
 
C backtrace follows:
(A real debugger may provide better information)
 
18112:  ./src/xemacs -q
 ef2b8604 waitid   (0, 46c1, efffe418, 3)
 ef2da5c8 waitpid  (46c1, efffe500, 3, ef311018, 48, 0) + 58
 ef2f0fb0 system   (efffe670, 163430, 1633c8, 46c0, 1028001c, 6849c) + 1d8
 000648a8 fatal_error_signal (1633c8, 0, efffe7b8, 0, 0, 0) + d4
 ef2b7d44 sigacthandler (6, 0, efffe7b8, ef311018, 18, 0) + 28
 ef2b95b4 abort    (40, 1645d8, 2ed, 1645e8, 0, 3ddba4) + c8
 00066724 assert_failed (1645d8, 2ed, 1645e8, 7fffffff, 2a11c8, 0) + 1c
 0006f658 event_to_character (ffffffff, 0, 0, 0, 0, 0) + a8
 000a9e58 event_matches_key_specifier_p (3ddba4, 7, 24ec00, 0, 0, 3ddc19) + 68
 000746bc next_event_internal (3ddba4, 1, 1, 10280004, efffede8, fffffff) + 1dc
 00074b30 Fnext_event (103ddba4, 10280004, 10280004, 24ec00, 10280004, 0) + 3f0
 00052324 Fcommand_loop_1 (10280004, 357d80, 10357d80, 6857c, 0, 0) + 1b4
 00052160 command_loop_1 (10280004, efffef08, 2035397c, 0, 0, 52144) + 1c
 000685d8 condition_case_1 (10280064, 52144, 10280004, 51aa4, 10280004, 0) + ec
 00051b98 command_loop_3 (0, effff070, 68208, 68210, 10280004, 0) + 28
 00051bc0 command_loop_2 (10280004, 0, 0, 251800, 51bbc, efffee50) + 4
 00068238 internal_catch (10292dbc, 51bbc, 10280004, 0, effff070, 0) + 98
 00051dc8 initial_command_loop (fffffff, 279000, 163400, 0, effff4a4, effff4a4) + 1f0
 00065a38 main_1   (2, effff33c, effff348, 0, 0, 0) + d78
 00066168 main     (2, effff33c, effff348, 24ab70, 1, 0) + a4
 0003ffac _start   (0, 0, 0, 0, 0, 0) + 5c
 

