So I upgraded to 12.10 and now I'm getting

Warning: program compiled against libxml 208 using older 207

I presume this has something to do with the Orbolt stuff….

anyways…did I make a big mistake upgrading…

Jim

Is something actually not working?

The warning itself does not say much. We have 12.10 running, but only headless on rendernodes.

nothing I've been able to see yet…wondering if anyone else had any problems with 12.10
Jim

nothing I've been able to see yet…wondering if anyone else had any problems with 12.10
Jim

I've seen the same warning message when launching H12.5 under Slackware 14.0 as well. I believe it's related to the packages GConf2 and libxml. If you upgrade to libxml 2.8.0 or later and recompile GConf2 3.2.6 it will go away.

Hi,

Houdini running in: Gentoo Linux: 3.10.25-gentoo x86_64

I've recently seen something similar in Houdini 13.0.314

• $ houdini
  Warning: program compiled against libxml 209 using older 208
  Warning: program compiled against libxml 209 using older 208
  and with Houdini 12.5.483
  $ houdini
  ./hbrowser-bin: /opt/hfs12.5.483/python/lib/libz.so.1: version `ZLIB_1.2.3.4' not found (required by /usr/lib/libpng16.so.16)
  Warning: program compiled against libxml 209 using older 207
  Warning: program compiled against libxml 209 using older 207
  Warning: program compiled against libxml 209 using older 207
  ./hbrowser-bin: /opt/hfs12.5.483/python/lib/libz.so.1: version `ZLIB_1.2.3.4' not found (required by /usr/lib/libpng16.so.16)
  Gentoo is linux built from source.
  libxml has been compiled with the following flags:
  # emerge -pv libxml2
  
  These are the packages that would be merged, in order:
  
  Calculating dependencies… done!
  dev-libs/libxml2-2.9.1-r1:2 USE=“icu ipv6 python readline -debug -examples -lzma -static-libs {-test}” PYTHON_TARGETS=“python2_7 python3_3 -python2_6 -python3_2” 0 kB
  This gentoo “emerge” command indicates libxml2 (version 2-2.9.1) has been compiled for python targets 2.7 and 3.3 (and not 2.6 or 3.2)
  
  Following a post by Neil78 http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=29185&highlight=libxml [sidefx.com] referencing a Wolfwood post I tried setting houdini environment vars:
  $ export HOUDINI_PYTHON_BIN=/opt/hfs13.0.314/python/bin/python2.7
  $ export HOUDINI_PYTHON_LIB=/opt/hfs13.0.314/python/lib/libpython2.7.so
  $ houdini
  $ Warning: program compiled against libxml 209 using older 208
  Warning: program compiled against libxml 209 using older 208
  Warning: program compiled against libxml 209 using older 208
  still there. Same is true if HOUDINI_PYTHON var's are set to python2.6
  
  Checking what libxml is installed with houdini:
  $ cd /opt/hfs13.0.314
  $ find . -iname ‘*libxml*’
  ./python/lib/libxml2.so.2.8.0
  ./python/lib/libxml2.so.2
  ./python/lib/libxml2.so
  ./dsolib/libxml2.so.2.8.0
  ./dsolib/libxml2.so.2
  ./dsolib/libcollada_LIBXMLPlugin.so
  ./dsolib/libxml2.so
  ./mozilla/components/libxmlextras.so
  ./toolkit/include/libxml
  ./houdini/help/licenses/libxml2.html
  ./houdini/help/licenses/libxml2.txt
  ./hsvg/libxml2.so.2.8.0
  ./hsvg/libxml2.so.2
  ./hsvg/libxml2.so
  It looks like the libxml shipped with Houdini 13.0.314 is “208” not “209” (?)
  
  b.