>>>> "KO" == Kevin Oberman
<oberman(a)es.net> writes:
KO> A couple of minor problems building 21.1.13. Configuration command:
KO> configure --without-gcc --with-gnu-make '--cflags=-fast -std'
--with-site-lisp --site-includes=/usr/local/include
I ported 21.2 to DEC C on Tru64 4.0, but didn't consider it important
enough to backport to 21.1, partly because gcc works. I am interested
in getting access to Tru64 5.0, if you could make that possible.
KO> First, configure refuses to recognize V5.0, so I had to build on an
KO> old V4.0e system.
You could try giving configure an explicit CONFIGURATION argument,
like
alphaev56-dec-osf4.0e
If you have the time, try building 21.1.13 with gcc, and 21.2.40 with
DEC C.
KO> Second, I regex.c would not compile. Type mismatch for alloca. I
KO> edited regex.c and modified line 289 which was "char *alloca" to
"void
KO> *alloca". That was the only compiling problem, but it failed several
KO> times in building the finder database. For some reason about 5 files
KO> in my /usr/local/lib/xemacs/xemacs-packages/list directories had 640
KO> protections, so could not be read. I'm baffled as to what happened
KO> there, but I chmoded them and the build completed.
KO> Note that the regex problem was the only compile problem I had using
KO> Tru64 C compiler. Is *alloca normally a char? Seems like void is what
KO> it should be. I'd try logging into my FreeBSD system and seeing how
KO> it's typed there, but the @Home connection seems to be down at the
KO> moment. :-(
You're right. Fix is already in 21.2.
KO> In any case, it looks pretty good. I really should have built from CVS
KO> before the release so the regex.c could have been patched. Sorry.
KO> Is there any hope of config.guess ever being updated to handle Tru64
KO> UNIX V5? (Yes, I realize that this is not really an XEmacs issue.)
What does 21.2's config.guess do?