Re: [Conky-development] Problem building 1.7.2

[paul m. <pa...@wa...>]

Hi Phil

Phil wrote:

> Please reply to the list address, otherwise there will be no way for
> others benefitting from this discussion.

Sorry about that - I expected reply-to to point to the list, failed to 
notice that it didn't. Should have remembered - I've been caught that 
way before.

> On Tue, Sep 08, 2009 at 12:57:29PM +0200, paul marwick wrote:
>> Phil wrote:
>>> Hi,
>>> On Mon, Sep 07, 2009 at 04:40:06PM +0200, paul marwick wrote:
>>>> I'm having problems getting conky 1.7.2 under both Zenwalk and Vector.
>>>>
>>>> Under Vector, even with lua installed, it fails, failing to find lua. 
>>>> With lua disabled, it fails at the same spot as the Zenwalk build - as 
>>>> below:
>>> You're sure you have toluapp (tolua++) installed? That was the problem
>>> on my system.
>> No. It isn't installed under either Zenwalk or Vector, but lua is found and 
>> used under Zenwalk, not under Vector. The same version of lua is installed 
>> in both - 5.14.
> 
> Well, that was just a guess out of the blue. The amount of information
> you specified hardly allows for more precise hints.

I'm aware of that. Trouble is, I don't have a great deal of information 
to provide. While the lua packages from Vector and Zenwalk are distro 
specific builds, there doesn't look to be much difference between them. 
Why one should be detected while the other isn't, I really don't know. I 
may try the Zenwalk package under Vector and see what happens then...

>>>> checking for iwlib.h... yes
>>>> checking for iw_sockets_open in -liw... no
>>>> configure: error: iw_sockets_open not found
>>>> make: *** No targets specified and no makefile found.  Stop.
>>>> build() failed.
>>>>
>>>> In both instances, the wireless-tools package is a Slackware-derived one, 
>>>> so I assume that the same problem would probably also affect Slackware.
>>>>
>>>> Any hints as to how to fix this?
>>> Looks like you're using an incompatible version of wireless extensions.
>>> The easiest solution would be to disable wireless support
>>> (--disable-wlan). Though I guess you've explicitly requested wireless
>>> support, so you will either have to provide more information about what
>>> software in which version you're using, or help yourself if you can.
>> Wireless tools installed are version 29 (the build from Slackware 12.1, I 
>> think. I can try rebuilding it, but without some idea of why its not 
>> working, I'm a bit stuck.....
> 
> It's not working because the libiw.so on your system lacks the symbol
> iw_sockets_open. Just as the error message says. So you probably want to
> find out if this symbol was either added in a later version (your
> libiw.so is too old) or dropped in favour of something else (your
> libiw.so is too new).

It looks as though there may be something odd about the wireless-tools 
build for Slackware. Checking, I don't have a libiw.so on the system - 
what I do have is a /usr/lib/libiw, which is a binary. Why that should 
be, I don't know. Trouble is, so far, I've not been able to find a copy 
of the SlackBuild used to produce the package, so I don't know what is 
being done to produce this, or why it is being done. I will try my own 
build (a quick compile of the sources does produce a libiw.so.29. 
Trouble is, I have no idea why the Slackware package does not. I will 
experiment (carefully) with my own build and see if that fixes the Conky 
buid. However, if it does, I am unlikely to be able to replace the 
existing build in either Vector or Zenwalk.

>> I'd really rather not disable the wlan support if possible - I use it, and 
>> I'm sure others do as well.
> 
> Yes, and the later tells me the problem is rather your system than
> conky. ;)

:) I can't argue with that. Trouble is, its not a problem that I can 
fix. Not to mention that it has always worked in the past - my current 
1.7.1.1 build works with wlan support on both Vector and Zenwalk. So it 
reflects something that has changed in Conky. My chances of getting 
Slackware, Zenwalk and Vector to change the wireless-tools package seems 
pretty remote....

Regards, Paul.