On Mon, Mar 14, 2011 at 10:44 AM, Johannes Ring <joha...@simula.no> wrote: > On Mon, Mar 14, 2011 at 10:40 AM, Garth N. Wells <gn...@cam.ac.uk> wrote: >> >> >> On 14/03/11 09:32, Johannes Ring wrote: >>> On Mon, Mar 14, 2011 at 5:00 AM, Johan Hake <johan.h...@gmail.com> wrote: >>>> Hello! >>>> >>>> I have now removed all traces of SWIG code for version < 2.0. >>>> Unfortunately I >>>> have not been able to test it at my buildbot, as the versions has diverged, >>>> due to a previous merge gone wrong. >>>> >>>> Johannes could you make a new branch of dolfin at my buildbot from >>>> >>>> lp:~dolfin-core/dolfin/hake >>>> >>>> and maybe push force build after that? >>> >>> Done. >>> >> >> Have all the buildbots been updated to SWIG 2.0? > > No, I'm working on it. Only mac-osx and linux64-exp have SWIG 2.0 at the > moment.
I have now upgraded SWIG to version 2.0 on the buildbots. The lucid-amd64 and maverick-i386 slaves, building dolfin-main, are using /usr/bin/swig2.0 from the Ubuntu package (backported from Natty), while the personal buildbots are using some locally installed SWIG. This results in errors like this on dolfin-main: OSError: PyDOLFIN was not compiled with the present version of swig. Install swig version 2.0.01 or recompiled PyDOLFIN with present swig How are we supposed to deal with this? I have used -DSWIG_EXECUTABLE:FILEPATH=/usr/bin/swig2.0 when building UFC and DOLFIN but how can this executable be specified when running the tests? Johannes _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
