|
Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://xmm.vilspa.esa.es/sas/7.1.0/watchout/7.1/sas_headas_init_order.shtml
Дата изменения: Unknown Дата индексирования: Sun Apr 13 05:48:44 2008 Кодировка: Поисковые слова: п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п п |
| Home | Documentation | Watchouts | Help | Calibration | Installation | Software requirements | Download |
There is a known incompatilility between SAS and HEASOFT/HEADAS regarding the order in which they are initialized first. When HEASOFT/HEADAS is initialized first and then SAS, everything works fine. By doing it the other way around, some SAS tasks do not work or produce segmentation faults.
The origin for such a behaviour is that both, SAS and HEASOFT/HEADAS modify the LD_LIBRARY_PATH variable (or the DYLD_LIBRARY_PATH in Mac OS X), to adapt it to its specific needs. That variable provides all executable binaries with a list of directory paths where they can search for shared libraries which they require to run. By initializing first HEASOFT/HEADAS and then SAS, SAS tasks binaries find the required shared libraries in the proper directories. The reverse order makes available specific HEASOFT/HEADAS libraries to some SAS tasks, which result incompatible with those required to run them properly.
Since HEASOFT/HEADAS tools are of great help to work with SAS, the rule is to initalize first HEASOFT/HEADAS, then SAS.
This problem did not occur with versions of HEASOFT/HEADAS prior to 6.0.