dolfin team mailing list archive

["Garth N. Wells" <gnw20@xxxxxxxxx>]

On 20 Dec 2011, at 20:07, Johan Hake <johan.hake@xxxxxxxxx> wrote:

> I just ran into a peculiar problem with JIT and pkconfig. I am on a CentOS 
> cluster with libxml2.dev on the frontend and on the nodes. JIT compiling a 
> dolfin extension module on the front end works fine, but JIT compiling on the 
> compute nodes does not work. 
> 
> For some reason, beyond me, the linker picks up the static library. All 
> libraries that comes with libxml included in the Libs: field in the package 
> config file.

> Strangly enough libxml-2.0 is also included in the Requires: 
> field. My problem went away when I removed libxml-2.0 from that field.
> 
> Which leave that field as: 
> 
>  Requires: ufc-1 
> 
> Anyone else have had that problem? Why is libxml-2.0 included in the Requires: 
> field in the first place?

Is this in dolfin.pc?

I guess we can get rid of it since libxml2 is included in the list of libs.

The sooner we get rid of pkg-config the better . . . 

Garth

> If no good reason I suggest we remove it.
> 
> Johan
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help   : https://help.launchpad.net/ListHelp