dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #25754
Re: Verbose printing of JIT compiler line
-
To:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
From:
Johan Hake <hake.dev@xxxxxxxxx>
-
Date:
Wed, 11 Jul 2012 12:45:46 +0200
-
Cc:
DOLFIN Mailing List <dolfin@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<CAA4C66OLG=_k8fZanVFkv5Ve4qrKzyNVxi8VDrmpCRVMy7MY1Q@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
Try:
from dolfin import *
import instant
instant.set_log_level(DEBUG)
Expression("x[0]")
and look for:
include_dirs: [...], library_dirs: [...],
libraries: [...], cppargs: [...],
These are the arguments that are gathered by dolfin and passed to
instant, using pkg-config. instant then writes a setup.py file, which
you can look at in:
.instant/chache/dolfin_compile_code_[...]/setup.py
Then distutils might add stuff too. This should be configurable though,
through some global config file.
Johan
On 07/11/2012 11:53 AM, Garth N. Wells wrote:
Is there a way to print the JIT compiler line? I've been running into
lots of JIT problems lately related to the choice of compiler and
flags, etc.
I think the root of the evil is that we're using pkg-config rather
than CMake to get the JIT options.
Garth
_______________________________________________
Mailing list: https://launchpad.net/~dolfin
Post to : dolfin@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~dolfin
More help : https://help.launchpad.net/ListHelp
References