On Sun, 08 Oct 2000 12:28:52 BST, Gunnar Evermann said:
 any ideas? 
Hmm.  I've been pretty quiet of late, I'll take a shot at this.  We don't
seem
to have many AIX experts lurking here. ;)
 I attempted to compile XEmacs-21.1.12 on AIX 4.3.2 
Oh?  There's evidence to the contrary...
 uname -a: AIX darwin 2 4 00600066C000 
uname thinks it's some variant of 4.2.
 XEmacs 21.1.8 "Bryce Canyon" configured for
`powerpc-ibm-aix4.2.1.0'. 
As does 'oslevel'.
 xemacs_21_1_12_powerpc_ibm_aix4_3_2_0() at 0x10001b68 
I have *NO* idea how we ended up here. with an 4_3_2 eyecatcher, if it
was built on a 4.2.1 system.
I'd do the following:
0) Double-check that the binary that crashed is the binary that was
built on the 4.2.1 system.
1) Rule out the possibility of a binary built on a 4.3.2 system and
somehow coerced to run on a 4.2.1 system (it *can* be done with enough
abuse of shared libraries, but will blow up gloriously if/when it tries
to do something that's 4.3.2-specific and doesn't have kernel support).
2) 'oslevel -q' to get the known levelsets (on my system, this gives:
Known Maintenance Levels
------------------------
4.3.3.0
4.3.2.0
4.3.1.0
4.3.0.0
3) Do (for instance) 'oslevel -l 4.3.3.0' to see what filesets are
backleveled.
4) If there are backleveled filesets, update them and try again.  If you
have enough 4.3.2 filesets installed that 'oslevel -q' shows 4.3.2.0 as
a known levelset, you really should get the REST updated to get in sync.
The current latest AIX is 4.3.3.0 "Maintenance Level 5".  Output of
an 'lslpp -L' at this level shows a lot of 4.3.3.25 level filesets...
-- 
				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech