Matthew Woehlke wrote:
> 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.
So, what is the fix? I'm lazy.
Anyway, when the curses library isn't found configure will continue.
This is because on a few platforms the functionality is included in the
standard libraries and Vim can be build anyway.
--
ALL: A witch! A witch!
WITCH: It's a fair cop.
ALL: Burn her! Burn her! Let's make her into a ladder.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
