🚀 go-pugleaf

In GNU Emacs 19.25.2 of Fri Aug 19 1994 on <censored node name> (rs6000-ibm-aix)

On an RS/6000 server model 530 running AIX 3.2.5, I configured emacs
19.25 with the --with-x-toolkit option, more specifically:

   configure rs6000-ibm-aix --with-x11 --with-x-toolkit --with-gcc=no --prefix=/home/gnu

and the final executable always dies immediately with SIGSEGV.  During
the build process, this shows up when an attempt to build the
blessmail script is made.  The actual location of death, as reported
by XCDB, was in a call to make_unint_string() in alloc.c:

  XSTRING (val)->size = length;
     (val was 0x034d6e3e)

make_unint_string() had been called by make_string() which had been
called by build_string(), which had been called by
set_process_environment(), which had been called by main().  The
temacs executable was usable, and the menus did seem like menus.  In
ignorance, I tried bumping PURESIZE way up, almost double, to no
avail.

Emacs 19.25, configured without the x-toolkit, worked just fine, as is
evidenced by this mail message.  Emacs 19.22, although beta, had
always worked as well.

FYI (probably not relevant).  XCDB, upon startup, reports the
following, for both the failing and working versions of emacs:

xcdb: bad BINCL in symbol 64031 (fixup attempted)
...This may be due to a linker problem covered by APAR IX30481.
...The Austin defect number is 69438 - "linker problem occurs when
...there is executable code contained in include files".
...I'll attempt to continue execution, but you may have difficulty
...stepping and breakpointing portions of some files.

{ Apologies if this is a duplicate.  I am not on the mailing list, and
we don't receive the newsgroup. }