32-bit builds?

[Raymond Toy]

While trying to do a build on Solaris (sparc), I ran into this
problem:

  Building finder database ...
  rm -f /net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp/finder-inf.el
  ./xemacs -no-packages -batch    -eval "(setq finder-compile-keywords-quiet t)" \
          -eval "(setq lisp-directory \"/net/gondor/Volumes/share2/src/xemacs/hg/xemacs-21.5/src/../lisp\")" \
          -l finder -f finder-compile-keywords

  Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)
  Loading auto-autoloads.el... (file auto-autoloads.elc is out-of-date)

  xemacs exiting.
  Invalid argument: No buffer named, "*finder-scratch*"

To see what was going on, I tried a 64-bit build using Sun C instead
of gcc 4.5.2.  This works fine and the result works ok too.  In case
this was a gcc issue, I tried again using Sun C to do a 32-bit build.
This fails in the same way.

As a final test, I tried a 32-bit build on Linux using gcc 4.4.1.  The
64-bit build works fine.  However, the 32-bit build fails miserably
with error messages like:

  gcc -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wshadow -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wdeclaration-after-statement  -Wunused-parameter -g  -m32  -Demacs -I. -I/net/gondor/src/xemacs/hg/xemacs-21.5/src -DHAVE_CONFIG_H /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c
  /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:107: warning: function declaration isn't a prototype
  /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:120: warning: function declaration isn't a prototype
  /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:130: warning: function declaration isn't a prototype
  /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:143: warning: function declaration isn't a prototype
  /net/gondor/src/xemacs/hg/xemacs-21.5/src/termcap.c:236: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ospeed'

Anyone doing 32-bit builds these days?  A 64-bit build is fine with
me, but I don't really need an editor that can edit multi-GB
files.:-) 

I also get a few warnings on 32-bit Solaris about integer overflows.
I'll check those out and see if they're important or not.

Ray