Notice: Undefined variable: name in /srv/http/vhosts/ on line 248

Package Details: libsbml 5.13.0-1

Git Clone URL: (read-only)
Package Base: libsbml
Description: XML-based description language for computational models in systems biology
Upstream URL:
Licenses: LGPL
Submitter: mschu
Maintainer: mschu
Last Packager: mschu
Votes: 5
Popularity: 0.083531
First Submitted: 2011-04-24 08:52
Last Updated: 2016-06-07 12:55

Latest Comments

jakobcreutzfeldt commented on 2014-06-13 09:40

The build fails for me (including on the latest version, 5.10.0) unless I override the Make parrallel-build argument (I have to add "-j1" to the "make" command in the build function).

mschu commented on 2013-03-20 17:02

I will update this once I get home (one week from now). If that's too late, please someone paste a PKGBUILD.

mschu commented on 2013-03-11 20:36

You are right, that must have gotten lost with the last update. Fixed.

Herk commented on 2013-03-11 20:31

Should not swig be a dependency? Without it I was not able to install the package.

mschu commented on 2013-02-04 10:05

Oops, uploaded the wrong PKGBUILD by mistake. Fixed now.

menta commented on 2013-02-04 10:02

The first line of the 'package' function should be changed to 'cd "$srcdir/$_pkgname-$pkgver-Source"'.

mschu commented on 2012-08-05 14:35

Updated to 5.6.0 and removed the CMake dependency. The reason it was used in the first place was that the flags for the bindings in configure were not working - they are now, so we can use it directly.

The issues with swig are said to be build issues in the link you provided. Building worked fine with the latest swig, so I'm keeping that.

I don't see an easy way to python 2 and 3 at the same time, so I'll leave it to build with python2 because most of the other simulation software has not moved to version 3 yet.

In general, you will not want to just use ./configure, make, and make install but to modify the PKGBUILD to your needs, because otherwise pacman can not track the files on your harddrive and the dependency tree.

essenceoffoo commented on 2012-08-04 08:40

Does it really make sense to use CMake directly? In the README.txt it says you can just use the old fashioned ./configure && make && make install. You can supply useful options at the configuration step that are much cleaner than the CMake-options (at least in my opinion).

I just installed it that way with ./configure options that are specific to my plans (but I didn't create a package).

The newest release (5.6.0) also works with Python3 (both building and binding)

Compatibility note: It may make sense to use an older version of swig (version 2.0.4 see ) for creating scripting language bindings.