gvim doesn't run

[Yan]

Hi, I just downloaded sources for vim72 and built them. vim works just
fine (at least there is no problem with that short set of features
that I use), but gvim doesn't start - says 'command not found'. I am
running Suse. I don't have yum installed, and when I tried installing
gvim through the rpms (vim, ruby, gvim) I ended up with some broken
version - syntax and more wouldn't work. So I decided to build from
source but like I said gvim executable doesn't seem to be generated. I
tried playing with the Makefile but I am not a big expert on build
process so that didn't help. Anyone knows what my problem is? Thanks!

[Yan Vinogradov]

I just tried the same on Ubuntu 8.04 and experience the same results - vim present but gvim is missing. Of course on Ubuntu I can just install vim-full package and don't bother building from source, but I am curious as to what I am doing wrong.

Thanks!

[sc]

On Monday 11 August 2008 16:20, Yan Vinogradov wrote:
> I just tried the same on Ubuntu 8.04 and experience the same results - vim
> present but gvim is missing. Of course on Ubuntu I can just install vim-full
> package and don't bother building from source, but I am curious as to what I
> am doing wrong.
>

yan--

it is possible the only "wrong" thing you are doing is
mis-interpreting what you are seeing after you build

there is no 'gvim' created from the build process

the install process, when properly performed, creates a
symbolic link to 'vim' with the -g option

sc

[Tony Mechelynck]

vim --version |more

If, near the top, it says "with [something] GUI" then:

cd /usr/local/bin
ln -sv vim gvim

similarly (if you want them) for view, gview, vimdiff, gvimdiff, etc.

see ":help ex" for all possible names. One of the reasons exim is often
not installed is that there is a mail routing program of the same name:
if you use it, it would create a name clash.

IIRC, when installing from the rpms you must always install at least two:

vim-common runtime files etc., always needed
vim-minimal a minimum version, without syntax highlighting and
without expression evaluation. It will always be
available as "vi" even in single-user emergency-
repairs mode and even if /usr is on a different
partition which you decide not to mount
vim-enhanced a console version, invoked as vim
vim-x11 a GUI version, invoked as gvim

If you compile it yourself, you will normally compile only a GUI version
(which, on Linux, can also run in console mode), it will be installed as
/usr/local/bin/vim and its runtimes in /usr/local/share/vim/vim72/

Best regards,
Tony.
--
Uppers are no longer stylish, methedrine is almost as rare as pure acid
or DMT. "Consciousness Expansion" went out with LBJ and it is worth
noting, historically, that downers came in with Nixon.
-- Dr. Hunter S. Thompson

[Gary Johnson]

Depending on how vim was configured, the install process may create
a symbolic link from gvim to vim in the bin directory in which vim
is installed. However, there is no way to include options in
symbolic links. Instead, vim looks at the name by which it was
invoked and internally sets options accordingly. See

:help ex

and scroll up a few lines to the line beginning, "The startup mode".

Regards,
Gary

[Dominique Pelle]

On Mon, Aug 11, 2008 at 11:20 PM, Yan Vinogradov <yvino...@gmail.com> wrote:

> I just tried the same on Ubuntu 8.04 and experience the same results - vim
> present but gvim is missing. Of course on Ubuntu I can just install vim-full
> package and don't bother building from source, but I am curious as to what I
> am doing wrong.
>
> Thanks!

Most certainly, you have not installed the required dev packages on Ubuntu
to build the GUI.

You can install them for example with something like:

sudo apt-get install libncurses5-dev libgnome2-dev \
libgtk2.0-dev libatk1.0-dev libbonoboui2-dev \
libcairo2-dev libx11-dev libxmp-dev libxt-dev

I have not tried, maybe some of them are missing in
the above list.

Other dev packages whose presense can affect which
features of Vim get built:

libacl1-dev libgpm1-dev

And more packages (I don't have the exhaustive list) if
you want Perl/Python (etc) support for example.,

Then do:

$ cd vim7
$ make distclean
$ ./configure --with-features=huge --enable-gui=gnome2
$ make
$ sudo make install

-- Dominique

[Yan Vinogradov]

Thanks everyone.

I tried invoking gvim by calling 'vim -g' and got the following error:

E25: GUI cannot be used: Not enabled at compile time

I looked through the Makefile under src directory and it seems like gui should be built in the default configuration - did I get that wrong? Does anyone know and could please tell me what do I need to modify in the Makefile (or elsewhere) to get the gui enabled at compile time?

Thanks!

[Ag. D. Hatzimanikas]

On Tue, Aug 12, at 10:13 Yan Vinogradov wrote:
> Thanks everyone.
>
> I tried invoking gvim by calling 'vim -g' and got the following error:
>
> E25: GUI cannot be used: Not enabled at compile time
>
> I looked through the Makefile under src directory and it seems like gui
> should be built in the default configuration - did I get that wrong? Does
> anyone know and could please tell me what do I need to modify in the
> Makefile (or elsewhere) to get the gui enabled at compile time?
>

Did you follow Dominique's guide? This is all you have to do.

When you run ./configure, vim tries to locate some libraries and headers
and if it finds them it builds the graphical interface (gui) *by default*.

I am not familiar with your distribution to suggest you with a complete
command to install the development packages, but I believe (looking
at the Dominique's message) the list is complete.

> >
> > You can install them for example with something like:
> >
> > sudo apt-get install libncurses5-dev libgnome2-dev \
> > libgtk2.0-dev libatk1.0-dev libbonoboui2-dev \
> > libcairo2-dev libx11-dev libxmp-dev libxt-dev
> >

and then:

> > $ cd vim7
> > $ make distclean
> > $ ./configure --with-features=huge --enable-gui=gnome2
> > $ make
> > $ sudo make install
> >

Perhaps, you could attach for the list members the "./configure" output
(only the interesting part if you can).

Regards,
Ag.

[Matt Wozniski]

On Tue, Aug 12, 2008 at 10:13 AM, Yan Vinogradov wrote:
> Thanks everyone.
>
> I tried invoking gvim by calling 'vim -g' and got the following error:
>
> E25: GUI cannot be used: Not enabled at compile time
>
> I looked through the Makefile under src directory and it seems like gui
> should be built in the default configuration - did I get that wrong? Does
> anyone know and could please tell me what do I need to modify in the
> Makefile (or elsewhere) to get the gui enabled at compile time?
>
> Thanks!

So, then, most likely ./configure couldn't find some of the necessary
development headers to build the gui, and decided to drop out that
feature for you. On an ubuntu system, you should be able to get the
headers you need with an "apt-get build-dep vim" and then redo from
the ./configure on.

~Matt

[sc]

which will probably work better if you first

rm src/auto/config.cache

sc

[John Little]

Dominique

> Most certainly, you have not installed the required dev packages on Ubuntu
> to build the GUI.
>

> sudo apt-get install libncurses5-dev libgnome2-dev \
>   libgtk2.0-dev libatk1.0-dev libbonoboui2-dev \
>   libcairo2-dev libx11-dev libxmp-dev libxt-dev

Thank you for this list, Dominique.

That last one, libxt-dev, provides the Intrinsic.h header which drives
the X or no X decision. I found it somewhat unobvious, and had to
wade through the config.log and then search for packages with
"Intrinsic".

Regards, John

[Richard Hartmann]

On Wed, Aug 13, 2008 at 00:53, John Little <John.B...@gmail.com> wrote:

> Thank you for this list, Dominique.

For software that does exist as a package, there is an even easier way:

apt-get build-dep foo

will install every build dep of foo (in the version in your repos). Cases
where this is not totally sufficient are very rare.

Richard