Packages listed here may be needed to compile Singularity, they are more geared toward 32-bit compiles, but don't let that discourage you, there should be 64-bit packages of these available, perhaps even under the same name. Flex and Bison are no longer necessary. You'll need to have git and mercurial(hg). For Arch Linux, you'll need to get python2, python3 will not work.
GCC version 4(minimum 4.9) is required as GCC version 5 will not work.
Platform can be either linux32 (will make archtype i686) or linux64 (will make archtype x86_64).
Configuration can be either Release (equivalent to our releases) or RelWithDebInfo (if you'd like assist us with resolving crash bugs).
Arch Linux users, and developers who wish their systems to have default versions of programs other than our requisites, may need to
Note: Replace # with the number of processor cores you wish to dedicate to compiling.
This is pretty much it. The viewer will be in the newview/packaged subdirectory.
Known issues and how to handle them
If you use an Ubuntu/Debian based distribution and get a linker error: /usr/bin/ld: error: cannot find -lfoo
It may be solved by running: locate libfoo.so
If the output shows nothing, you're missing a package, ask your package manager for it.
If it shows something like /usr/lib/[arch]/libfoo.so.b.a.r or /usr/lib/[arch]/libfoo.so.b but not /usr/lib/[arch]/libfoo.so, you'll need to create a link, run sudo ln -s /usr/lib/[arch]/libfoo.so.b /usr/lib/[arch]/libfoo.so and your problem shall be solved.
The make command may error out the first time, just run it again. If this still doesn't quite work, file a JIRA.
If you run singularity as
If the crash was elsewhere, preferably in our code or libc, more information can get gained from it! You can do the following to produce a bunch of output which will hopefully make sense to me:
After you quit, you will find gdb.txt containing all output. Please send that to me :)
Open a terminal to the repository you cloned and check if there's an update by running:
If there is an update, there will be output from the command as it receives changesets.
To receive the update run:
To have the build number change for certain:
Knowledge Base >