On Wed, Feb 13, 2013 at 4:25 PM, Charles Campbell
<[log in to unmask]> wrote:
> Nico Kadel-Garcia wrote:
>>
>> On Wed, Feb 13, 2013 at 10:03 AM, Charles Campbell
>> <[log in to unmask]> wrote:
>>>
>>> Hello!
>>>
>>> My computer at work has been set to do automatic updates, and I generally
>>> try to keep my version of vim "on the bleeding edge". However, on Feb 1 I
>>> was no longer able to compile vim with gui-enabled using gtk, shortly
>>> after
>>> automatic updates were set up.
>>
>> If you're not keeping the vim build structure on the bleeding edge as
>> well, for example by using up-to-date SRPM's, you won't get new
>> dependencies reported. Are you building from a Fedora SRPM, or what?
>>
> I'm building vim using Bram Moolenaar's copy at ftp.home.vim.org , cd
> /pub/vim/unix, vim-7.3.tar.bz2,  and patches he provides for vim development
> (under /pub/vim/patches/7.3).  Bram Moolenaar is the author of vim.
>
> The code compiled and linked to gtk2  until recently (about Feb 1, which
> corresponds to patch#799); none of the patches since 799 have had anything
> to do with causing missing header files in /usr/include.  There was,
> however, a change to using automatic updates at that time.
>
> Regards,
> C Campbell

Just out of curiousity, I grabbed the SRPM for this version of vim
from Fedora 18 and tried to buidl it on RHEL 6. It looks like Bram
is.... doing some interesting things trying to outsmart the built-in
definitions for tgetstr and a lot of other low level terminal
functions. But the fact that it builds on Fedora 18, and not on RHEL
6, hints that the gtk change or other library changes since RHEL 6 are
conflicting with this.

This.... is a known problem of using a "stable" release.  The small
changes in the build environment make building bleeding edge versions
of tools more and more awkward.