On Wed, Jun 22, 2016 at 08:26:45PM +0200, Tony Mechelynck wrote:
> Hm, apparently zypper/apt-get is missing the Vim sources, which are
> found in a different repository than the rest. The URL for the Leap
> 42.1 Source (OSS) repository is
>
Hm, apparently zypper/apt-get is missing the Vim sources, which are
found in a different repository than the rest. The URL for the Leap
42.1 Source (OSS) repository is
http://download.opensuse.org/source/distribution/leap/42.1/repo/oss --
you can add it by URL with the YaST "Software → Software
On Wed, Jun 22, 2016 at 01:55:50PM +0200, Tony Mechelynck wrote:
> On Wed, Jun 22, 2016 at 12:08 PM, John Little wrote:
> > On Tuesday, June 21, 2016 at 7:13:46 PM UTC+12, Tony Mechelynck wrote:
> >> On Mon, Jun 20, 2016 at 3:46 AM, John Little
On Wed, Jun 22, 2016 at 12:08 PM, John Little wrote:
> On Tuesday, June 21, 2016 at 7:13:46 PM UTC+12, Tony Mechelynck wrote:
>> On Mon, Jun 20, 2016 at 3:46 AM, John Little wrote:
>> [...]
>> > I'm on a debian-derived distro, [...]
>>
>> Then
On Tuesday, June 21, 2016 at 7:13:46 PM UTC+12, Tony Mechelynck wrote:
> On Mon, Jun 20, 2016 at 3:46 AM, John Little wrote:
> [...]
> > I'm on a debian-derived distro, [...]
>
> Then you may have one bit of useful information. Which command would
> you run using
On Mon, Jun 20, 2016 at 3:46 AM, John Little wrote:
[...]
> I'm on a debian-derived distro, [...]
Then you may have one bit of useful information. Which command would
you run using aptitude or apt-get, to make sure that you have all
requirements for building Vim with
To mention the obvious just in case, are you running (in the vim src)
make reconfig
Sometimes that's necessary due to OS updates, without vim changing.
Regards, John Little
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
On Monday, June 20, 2016 at 12:33:07 PM UTC+12, toothpik wrote:
> looking for a module named something like gtk+-2.0.pc
> of course I have no such module in any of those directories
I'm on a debian-derived distro, so this may not be directly helpful, but for me
On Sun, Jun 19, 2016 at 07:33:00PM -0500, toothpik wrote:
> On Sun, Jun 19, 2016 at 03:23:09PM -0700, John Little wrote:
> yes, I saw pkg-config -- it apparently searches a series of directories
>
> /usr/lib/pkgconfig
> /usr/share/pkgconfig
> /usr/local/lib/pkgconfig
>
The GTK check uses the "pkg-config" command. I suggest you look in the
generated "configure" script in the auto directory to see what parameters it is
being given, then run it yourself, and report the parameters and result here.
Regards, John Little
--
--
You received this message from the
On Fri, Jun 17, 2016 at 10:34:34PM +0200, Tony Mechelynck wrote:
> On Fri, Jun 17, 2016 at 2:54 PM, toothpik wrote:
> > On Fri, Jun 17, 2016 at 10:01:14AM +0200, Tony Mechelynck wrote:
> >> On Fri, Jun 17, 2016 at 2:29 AM, toothpik wrote:
> >> > On Thu,
On Fri, Jun 17, 2016 at 2:54 PM, toothpik wrote:
> On Fri, Jun 17, 2016 at 10:01:14AM +0200, Tony Mechelynck wrote:
>> On Fri, Jun 17, 2016 at 2:29 AM, toothpik wrote:
>> > On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
>> >> Check the
On Fri, Jun 17, 2016 at 10:01:14AM +0200, Tony Mechelynck wrote:
> On Fri, Jun 17, 2016 at 2:29 AM, toothpik wrote:
> > On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
> >> Check the console output from configure if you still have it, or else
> >> the
On Fri, Jun 17, 2016 at 2:29 AM, toothpik wrote:
> On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
>> Check the console output from configure if you still have it, or else
>> the src/auto/config.log (or src/shadow/auto/config.log if you build in
>> a shadow
On Thu, Jun 16, 2016 at 11:59:46PM +0200, Tony Mechelynck wrote:
> Check the console output from configure if you still have it, or else
> the src/auto/config.log (or src/shadow/auto/config.log if you build in
> a shadow directory) which is more verbose. What exactly does configure
> not find that
Check the console output from configure if you still have it, or else
the src/auto/config.log (or src/shadow/auto/config.log if you build in
a shadow directory) which is more verbose. What exactly does configure
not find that it should?
I have no problem building Vim with GTK2 on openSUSE Leap
suddenly I am having trouble getting config to find either gtk+2 or +3
yast assures me I have the latest gtk2-devel and gtk3-devel
has something changed?
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
17 matches
Mail list logo