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', whic
mwoehlke wrote:
[snip]
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).
For the record, I did solve the "can't find 'ncurses'" problem... I
needed LDFLAGS="-L", and it
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,
(re-send because I forgot to CC vim-dev; sorry)
Bram Moolenaar wrote:
Matthew Woehlke wrote:
[snip]
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.
Goodness, I'll say. :)
vim/config
mwoehlke 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
A.J.Mechelynck wrote:
mwoehlke 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 sh
