On Tue, Mar 13, 2018 at 9:32 PM, Charles E Campbell
<drc...@campbellfamily.biz> wrote:
> Hello:
> I used the following configuration command:
>    ./configure --with-features=huge --enable-gui=gtk2 --enable-perlinterp
> --enable-pythoninterp --enable-rubyinterp --enable-cscope
> The vim I ended up with did not have gui enabled, although I only see two
> lines associated with gtk/gui/gvim in configure's output:
>    checking --enable-gui argument... GTK+ 2.x GUI support
>    checking --disable-gtktest argument... gtk test enabled
> I did the configure on a new  Scientific Linux release 7.4 (Nitrogen)
> system.
> Any hints on how to get gui enabled?
> Thank you,
> Chip Campbell

My guess is that some "development" package, needed to build the GUI,
is not installed on your system. It might be a GTK-related development
package or an X11-related development package, since Vim with GTK GUI
cannot be built without X11 but Vim without GUI can.

If you logged the stdout output from configure, search it
case-independently for the strings "gtk" or "x11", or even for the
word "headers". If you didn't log that, or if you lost that log, there
is a file auto/config.log in the same directory as auto/configure,
auto/config.status et al. It is more verbose than the stdout log, and
therefore a little more difficult to use, but it contains everything
that configure displayed on stdout (plus, among others, the sources of
all the test programs whose compilation or link ended in an error).

Best regards,

You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to