Difference between revisions of "Documentation/Nightly/Developers/FAQ/Building"

From Slicer Wiki
Jump to: navigation, search
m (Created page with '<noinclude>{{documentation/versioncheck}}</noinclude> <noinclude>__TOC__ ={{#titleparts: {{PAGENAME}} | | -1 }}=</noinclude><includeonly> ='''Developer FAQ: {{{1}}}'''= </include…')
 
Line 8: Line 8:
  
 
If QtSDK installer hangs, use <code>-style cleanlooks</code> command line option. For details, see [http://http://qt-project.org/forums/viewthread/17040/#85212 here].
 
If QtSDK installer hangs, use <code>-style cleanlooks</code> command line option. For details, see [http://http://qt-project.org/forums/viewthread/17040/#85212 here].
 +
 +
== Which minimum version of GLIBC is needed to build Slicer ? ==
 +
 +
The minimum version of GLIBC required to build Slicer is defined by the minimum version required by the pre-compiler binaries used when building Slicer. In our case, a small pre-compiled executable called the [http://www.commontk.org/index.php/Tools:_Application_launcher#What_is_CTK_Application_Launcher_.3F CTK AppLauncher] is downloaded [1] and used at configure and build time each time python has to be invoked.
 +
 +
The precompiled CTKAppLauncher imposes the following requirements regarding GLIBC and GLIBCXX libraries installed on your system:
 +
 +
<pre>
 +
$ strings CTKAppLauncher | ack GLIBC
 +
GLIBC_2.2.5
 +
GLIBCXX_3.4.11
 +
GLIBCXX_3.4.9
 +
GLIBCXX_3.4
 +
GLIBC_2.3.3
 +
GLIBC_2.3.2
 +
GLIBC_2.4
 +
GLIBC_2.3
 +
</pre>
 +
 +
 +
To check that your system provides the required GLIBCXX and GLIB versions, you could run the following command:
 +
 +
<pre>
 +
$ strings /usr/lib/libstdc++.so.6 | grep GLIBCXX
 +
GLIBCXX_3.4
 +
GLIBCXX_3.4.1
 +
GLIBCXX_3.4.2
 +
GLIBCXX_3.4.3
 +
GLIBCXX_3.4.4
 +
GLIBCXX_3.4.5
 +
GLIBCXX_3.4.6
 +
GLIBCXX_3.4.7
 +
GLIBCXX_3.4.8
 +
GLIBCXX_3.4.9
 +
GLIBCXX_3.4.10
 +
GLIBCXX_3.4.11
 +
GLIBCXX_3.4.12
 +
GLIBCXX_3.4.13
 +
GLIBCXX_3.4.14
 +
GLIBCXX_3.4.15
 +
GLIBCXX_3.4.16
 +
GLIBCXX_3.4.17
 +
</pre>
 +
 +
<pre>
 +
$ strings /lib/libc.so.6 | grep GLIBC
 +
GLIBC_2.2.5
 +
GLIBC_2.2.6
 +
GLIBC_2.3
 +
GLIBC_2.3.2
 +
GLIBC_2.3.3
 +
GLIBC_2.3.4
 +
GLIBC_2.4
 +
GLIBC_2.5
 +
GLIBC_2.6
 +
GLIBC_2.7
 +
GLIBC_2.8
 +
GLIBC_2.9
 +
GLIBC_2.10
 +
GLIBC_2.11
 +
</pre>
 +
 +
 +
[1] https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_CTKAPPLAUNCHER.cmake
 +
 +
 +
== How to

Revision as of 15:16, 11 September 2013

Home < Documentation < Nightly < Developers < FAQ < Building


For the latest Slicer documentation, visit the read-the-docs.


Building

What to do if QtSDK installer hangs ?

If QtSDK installer hangs, use -style cleanlooks command line option. For details, see here.

Which minimum version of GLIBC is needed to build Slicer ?

The minimum version of GLIBC required to build Slicer is defined by the minimum version required by the pre-compiler binaries used when building Slicer. In our case, a small pre-compiled executable called the CTK AppLauncher is downloaded [1] and used at configure and build time each time python has to be invoked.

The precompiled CTKAppLauncher imposes the following requirements regarding GLIBC and GLIBCXX libraries installed on your system:

$ strings CTKAppLauncher | ack GLIBC
GLIBC_2.2.5
GLIBCXX_3.4.11
GLIBCXX_3.4.9
GLIBCXX_3.4
GLIBC_2.3.3
GLIBC_2.3.2
GLIBC_2.4
GLIBC_2.3


To check that your system provides the required GLIBCXX and GLIB versions, you could run the following command:

$ strings /usr/lib/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
$ strings /lib/libc.so.6 | grep GLIBC
GLIBC_2.2.5
GLIBC_2.2.6
GLIBC_2.3
GLIBC_2.3.2
GLIBC_2.3.3
GLIBC_2.3.4
GLIBC_2.4
GLIBC_2.5
GLIBC_2.6
GLIBC_2.7
GLIBC_2.8
GLIBC_2.9
GLIBC_2.10
GLIBC_2.11


[1] https://github.com/Slicer/Slicer/blob/master/SuperBuild/External_CTKAPPLAUNCHER.cmake


== How to