dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #26261
Re: JIT unit test and OSX
-
To:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
From:
Johan Hake <hake.dev@xxxxxxxxx>
-
Date:
Sat, 19 Jan 2013 23:48:00 +0100
-
Cc:
DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAA4C66M1w=nccSKnOTVTBbCDuD=Bp9e1rSh1bheqg864XO-_kQ@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
On 01/19/2013 10:46 PM, Garth N. Wells wrote:
> I've got all of DOLFIN and the unit tests working nicely with OSX 10.8
> / Macports / clang, except the JIT unit test
>
> test_compile_extension_module
>
> I have no idea how to debug it. The seg fault is triggered by the line
>
> VecExp(*x);
>
> My best guess is that the pkg-config linking is bad. Any other ideas
> or suggestions on how to fix it?
Do you have several libpetsc installed?
> Can we finally get rid of the pkg-config garbage and use CMake for the
> jit linking?
It might be a combination of pkg-config and distutils. In the latter
library_dirs and libraries are two different arguments to the Extension
class. This means that we split the library dirs and libraries from each
other destroying all information about library_dir to library order.
This is actually preserved in the pkg-config file.
If we are going to shift to CMake we need not only ditch pkg-config, but
also distutils. Kent has added support for CMake compilation for VTK and
ITK based modules, which more easily is find using find_package calls.
I can have a look at this next week. I think using CMake instead of
distutils also opens up for easier compiler configurations, as this can
be quite obscure in distutils.
Johan
> Garth
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References