[jira] [Commented] (ARROW-7893) [Developer][GLib] Document GLib development workflow when using conda environment on GTK-based Linux systems

["Wes McKinney (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095966#comment-17095966 ] 

Wes McKinney commented on ARROW-7893:
-------------------------------------

I found out the solution to this. The problem occurs when using {{pkg-config}} installed by conda rather than the pkg-config provided by the host Linux system. If someone is developing using glib provided by conda then using the conda-provided pkg-config should work. 

So the fact that pkg-config is in https://github.com/apache/arrow/blob/master/ci/conda_env_cpp.yml is what's causing the problem. Running {{conda remove pkg-config}} resolved the issue I cited above. I'm not sure what can be documented better about this but it's at least some conclusion

> [Developer][GLib] Document GLib development workflow when using conda environment on GTK-based Linux systems
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-7893
>                 URL: https://issues.apache.org/jira/browse/ARROW-7893
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Documentation, GLib
>            Reporter: Wes McKinney
>            Assignee: Kouhei Sutou
>            Priority: Major
>             Fix For: 1.0.0
>
>
> I periodically deal with annoying errors like:
> {code}
> checking for GLIB - version >= 2.32.4... 
> *** 'pkg-config --modversion glib-2.0' returned 2.58.3, but GLIB (2.56.4)
> *** was found! If pkg-config was correct, then it is best
> *** to remove the old version of GLib. You may also be able to fix the error
> *** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
> *** /etc/ld.so.conf. Make sure you have run ldconfig if that is
> *** required on your system.
> *** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
> *** to point to the correct configuration files
> no
> configure: error: GLib isn't available
> make: *** No targets specified and no makefile found.  Stop.
> make: *** No rule to make target 'install'.  Stop.
> Traceback (most recent call last):
> 	2: from /home/wesm/code/arrow/c_glib/test/run-test.rb:30:in `<main>'
> 	1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
> /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- gi (LoadError)
> {code}
> The problem is that I have one version of glib on my Linux system while another in the activated conda environment, it seems that there is a conflict even though {{$PKG_CONFIG_PATH}} is set to ignore system directories
> https://gist.github.com/wesm/e62bf4517468be78200e8dd6db0fc544



--
This message was sent by Atlassian Jira
(v8.3.4#803005)