Crossfire Discussion List ()

David McIlwraith | 15 Feb 2012 10:22

Re: GTK client compilation issue w/ newer autotools

Hi,

Thanks. Seems that is the case here. X libraries are not listed in the
gtk+-2.0.pc file for some reason.

Regards,
- David McIlwraith <2c93e8f1 <at> gmail.com>

On Wed, Feb 15, 2012 at 3:16 PM, Mark Wedel <mwedel <at> sonic.net> wrote:
> On 02/14/12 04:49 PM, David McIlwraith wrote:
>>
>> Hi,
>>
>> X_LIBS does not appear to include libX11 with bleeding-edge auto*
>> tools; I am not sure if this is an issue with the client source itself
>> or a problem elsewhere. Nonetheless, on svn r16896 (up-to-date local
>> ArchLinux [x86_64] system), configure.ac must be modified such that
>> -lX11 is added in a similar vein to Xext. Noting that I have not
>> encountered this issue before when packaging the client, I am unsure
>> as to where the problem lies -- does anyone have any insight here?
>
>
>  Does pkg-config exist on the system (it may not - it seems like every few
> years yet a new method of determine package information comes out).
>
>  It would be interesting to see what 'pkg-config --libs gtk+-2.0' comes back
> with - that should provide the libraries that gtk+ needs.  For example, on
> my solaris system, I get:
>
> pkg-config --libs gtk+-2.0

(Continue reading)

headers

Mark Wedel | 26 Feb 2012 06:48

Re: GTK client compilation issue w/ newer autotools

On 02/15/12 01:22 AM, David McIlwraith wrote:
> Hi,
>
> Thanks. Seems that is the case here. X libraries are not listed in the
> gtk+-2.0.pc file for some reason.

  There isn't a lot the client can/should do in that case.

  One can set LIBS environmental variables to add extra libraries that are 
needed - I think in this case, that is probably the correct fix (well, workaround).

  While the client configure script could look for these other libraries, there 
is reasonably likelihood that it will break in various cases - if gtk+ adds 
another library dependency in the future, or if there is an extra one on some 
system.

>
> Regards,
> - David McIlwraith<2c93e8f1@...>
>
> On Wed, Feb 15, 2012 at 3:16 PM, Mark Wedel<mwedel@...>  wrote:
>> On 02/14/12 04:49 PM, David McIlwraith wrote:
>>>
>>> Hi,
>>>
>>> X_LIBS does not appear to include libX11 with bleeding-edge auto*
>>> tools; I am not sure if this is an issue with the client source itself
>>> or a problem elsewhere. Nonetheless, on svn r16896 (up-to-date local
>>> ArchLinux [x86_64] system), configure.ac must be modified such that
>>> -lX11 is added in a similar vein to Xext. Noting that I have not

(Continue reading)

headers

David McIlwraith | 26 Feb 2012 10:04

Re: GTK client compilation issue w/ newer autotools

Yes. I agree there, in relation to potential duplication of
dependencies inter alia; I am not entirely sure who is responsible for
the erroneous .pc file in current builds of ArchLinux, but a patch is
already present in the client 'crossfire-client-svn' package at
https://aur.archlinux.org/.  Thanks for your advice! 

Regards,
- David McIlwraith <2c93e8f1 <at> gmail.com>

On Sun, Feb 26, 2012 at 1:48 PM, Mark Wedel <mwedel <at> sonic.net> wrote:
> On 02/15/12 01:22 AM, David McIlwraith wrote:
>>
>> Hi,
>>
>> Thanks. Seems that is the case here. X libraries are not listed in the
>> gtk+-2.0.pc file for some reason.
>
>
>  There isn't a lot the client can/should do in that case.
>
>  One can set LIBS environmental variables to add extra libraries that are
> needed - I think in this case, that is probably the correct fix (well,
> workaround).
>
>  While the client configure script could look for these other libraries,
> there is reasonably likelihood that it will break in various cases - if gtk+
> adds another library dependency in the future, or if there is an extra one
> on some system.
>
>

(Continue reading)