JHP> uname -a: OSF1 goedel2 V5.0 1094 alpha JHP> The sysadmins here just upgraded the system software, changing the JHP> system from 'alphaev5-dec-osf4.0f' to 'alphaev5-dec-osf5.0f'. As a JHP> result, XEmacs doesn't build out of the box. It's easy to get it to JHP> build -- you just pass configure the argument 'alphaev5-dec-osf4.0f' JHP> and it works fine. JHP> I'd be tempted to suggest adding a file src/s/decosf5-0.h consisting JHP> only of JHP> #include "decosf4-0.h" JHP> and also making the appropriate change in configure, but I don't know JHP> if there are important differences between osf4.0 and osf5.0 that need JHP> to be taken into account. I also don't really know anything about JHP> configure scripts, so I probably wouldn't do it quite right if I did JHP> it myself. Anyone else? As always, I ask for access to your machine for testing. I hate adding stuff to s&m. I prefer the following solution; please test: (i.e. autoconf; configure; make) ./ChangeLog: 2000-10-06 Martin Buchholz <martin(a)xemacs.org&gt; * configure.in: Pretend that DEC OSF >= 5 is really DEC OSF 4. Index: configure.in =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/configure.in,v retrieving revision 1.111.2.125 diff -u -w -r1.111.2.125 configure.in --- configure.in 2000/10/03 06:31:24 1.111.2.125 +++ configure.in 2000/10/06 05:57:32 ＠＠ -1108,7 +1108,7 ＠＠ *-dec-osf1.2 | *-dec-osf1* ) opsys=decosf1-2 ;; *-dec-osf3.[[2-9]] ) opsys=decosf3-2 ;; *-dec-osf3* ) opsys=decosf3-1 ;; - *-dec-osf4* ) opsys=decosf4-0 ;; + *-dec-osf[[4-9]]* ) opsys=decosf4-0 ;; dnl DEC Ultrix *-*-ultrix[[0-3]].* | *-*-ultrix4.0* ) opsys=bsd4-2 ;;