Difference between revisions of "Library conflicts"

From Dynamo
Jump to navigation Jump to search
Line 23: Line 23:
 
Some systems report a conflict when trying to generate graphical output in the Linux  standalone:
 
Some systems report a conflict when trying to generate graphical output in the Linux  standalone:
  
  <nowiki> Error using axes
+
  <nowiki>Error using axes
 
While setting property 'Parent' of class ''Axes'':
 
While setting property 'Parent' of class ''Axes'':
 
Can't load '<your installation path>/MCRLinux/bin/glnxa64/libmwosgserver.so': dlopen: cannot load any more object with static TLS</nowiki>
 
Can't load '<your installation path>/MCRLinux/bin/glnxa64/libmwosgserver.so': dlopen: cannot load any more object with static TLS</nowiki>

Revision as of 12:20, 3 May 2018

Here we will list some of the problems found when installing/activating Dynamo.

Conflicting libstdc installations

Problem Some programs (specially the core of the GPU computations) cannot link to GLIBCXX.3.4.21 or some other number. This might happen both in Matlab or standalone modus.

Solution

Type in your linux shell

LD_PRELOAD="/usr/lib/x86_64-linux-gnu/libstdc++.so.6" 

or, correspondingly for bash shell

 export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libstdc++.so.6

(or the equivalent in your system) before starting Matlab (or Dynamo in the standalone)

Graphic depiction problems in the standalone

Some systems report a conflict when trying to generate graphical output in the Linux standalone:

Error using axes
While setting property 'Parent' of class ''Axes'':
Can't load '<your installation path>/MCRLinux/bin/glnxa64/libmwosgserver.so': dlopen: cannot load any more object with static TLS

These kind of errors can be solved by preloading the library before calling the Dynamoconsole by dynamo

 export LD_PRELOAD=<your installation path>/MCRLinux/bin/glnxa64/libmwosgserver.so