Re: v21 under HPUX -- gcc flags to be noted or standardized?
Karl Kleinpaste <karl(a)justresearch.com> writes in xemacs-beta(a)xemacs.org:
Darryl Okahata <darrylo(a)sr.hp.com> writes:
> OK, I've just compiled Pyrenean using an old gcc 2.8.1, and it
> seems to work fine.
Interesting. It might be useful to know why your build worked so
readily, whereas I've had maybe a dozen failures in the last couple
days when trying variations on "-g -O3 -Wall -Wno-switch", as auto-
selected (usually, and certainly initially) by configure. Also, why
the 20.4 builder (Marcus Thiessel <thiessel(a)rhrk.uni-kl.de>) chose the
long, involved set of options I've subsequently used with success.
If it matters, the machine in question has gcc 2.7.2, with
"uname -a"
showing "HP-UX clyde A.09.07 A 9000/735 2010262023 two-user license".
Strictly a gcc age issue, perhaps?
Perhaps. I did a mildly recent build of XEmacs 21 on HP/UX 10.20 a few
months ago with gcc-2.8.1 (from gcc binaries that are available off
the 'net somewhere) and it went without a hitch. I used the configure
options:
./configure --debug=no --error-checking=none --with-gcc \
--with-scrollbars=lucid --with-menubars=lucid \
--with-dialogs=motif '--cflags=-g -fno-caller-saves -O3' --with-pop