I found a really annoying problem trying to build VIM 7 on HP-UX. I have
an automated script that builds VIM as part of a toolchain. It ran
through, and to my surprise and annoyance, installed VIM in /usr/local
instead of where I wanted it.
Long story short, the script called 'configure', which failed because it
isn't (for some reason I have not yet figured out) finding the ncurses I
built (--with-tlib=ncurses). Now, '<root>/configure' calls
'src/configure' which calls 'src/auto/configure'... but the exit status
is not preserved AT EITHER STEP. As a result, my script thinks
'configure' succeeded and moves on to 'make', which RE-runs 'configure'
with default parameters, succeeds, and ultimately allows the script to
move on to 'make install'!
THIS IS BAD! The indirect 'configure' scripts need to preserve the exit
status.
The fix, which is trivial, I leave as an exercise.
Otherwise, having a VIM with working highlighting and WORKING KEYS on
the almost-half-dozen platforms I work on is wonderful. :-) Even if I've
only managed builds for four of them so far...
--
Matthew
Do not expose to extreme heat, cold, or open flame.
