Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.mrao.cam.ac.uk/~bn204/alma/sweng/casabuild.html
Дата изменения: Mon Apr 4 13:47:51 2016 Дата индексирования: Sun Apr 10 09:42:47 2016 Кодировка: ISO8859-5 Поисковые слова: molecular cloud |
See also
Missing symbols with names similar to pgsbox
, e.g., a dynamic
loading error of type:
ImportError: /home/bnikolic/d/n/casa-nrao/main/code/build/test/libncasa-display.so: undefined symbol: pgsbox_
are due to an incorrect link with one of the libraries that are part of WCSlib. Note that wcslib needs to be compiled -fPIC for linking to work correctly, and it apparently fails to be compiled in this way on some platforms/compilers (see also Position independent code).
There are two separate sources of IDL files within CASA:
Tools are defined by the *.xml
files in the xmlcasa/implement
sub-directory.
This is a description of the process by which Python loads external dynamic modules: http://www.python.org/doc/2.5.2/ext/methodTable.html.
One implication of this is that the name of the shared dynamic library
generated by the casa build system has to be casac.so
to be
loaded in Python, since the initialisation function has this name.
Usually occurs if there is a mismatch between versions of numpy which was picked up in the header files and the shared library. On appcd:
export PYTHONPATH=/home/bnikolic/d/p/cs/lib64/python/:$PYTHONPATH
This appears to be a component of IPython involved in parallel execution. (I do not see how parallelism at this granularity is useful for normal processing of astronomical data though...) It is referenced in casa.py.
See taskinit.py
, line:
casalog.setglobal(True)
creates it. Complete crash otherwise.
Separate application, casabrowsetable script
The following need to be linked in although this may not be obvious: