The path to the libraries needed by these compilers (for example):Įxport LD_LIBRARY_PATH=/opt/rh/devtoolset-9/root/usr/lib You will likely also need to update your LD_LIBRARY_PATH to include In the next step, set the compiler variables accordingly (for example):Įxport CC=/opt/rh/devtoolset-9/root/usr/bin/gccĮxport CXX=/opt/rh/devtoolset-9/root/usr/bin/g++Įxport FC= /opt/rh/devtoolset-9/root/usr/bin/gfortran Locate the devtoolset-9 installed directories: In building HEASoft, in the following way (for example): Note for users of CentOS 7.x: On CentOS 7, the default GNUĬompiler suite is v4.8, which is not supported for building HEASoft.ĬentOS 7 users may install a newer 'devtoolset' compiler suite for use PATH variable to remove the offending characters. Initialization will fail as a result, so users need to modify their Some users of WSL on Windows may have PATH environment variables thatĬontain directory paths containing double quotes ("). This can typically be resolved by putting /usr/bin at theįront of your PATH environment variable (as recommended in Ld: unsupported tapi file type '!tapi-tbd' in YAML file '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/lib/libSystem.tbd' for architecture x86_64 The CLT, then uninstalling and reinstalling the Homebrew compilers.Īnother common problem in the configure stage is the following: Since these third-party compilers use theĬLT, they must typically be rebuilt/reinstalled whenever XCode/CLTįor example, some users have worked their way past this by Tools (CLT), for example if you updated the CLT but did not reinstall Or MacPorts) is out-of-synch with the Apple (XCode) Command Line This error typically implies that your compiler suite (e.g. The HEASoft configure script may fail with "C compiler cannot createĮxecutables", and one of the config.logs may show Mac "C compiler cannot create executables":.So users encountering this issue are advised to update to v5.3.0 PleaseĬonsider using the 'Q' format for your file.", even if the file isĪffected versions of AstroPy appear to beĥ.0.5, 5.0.6, 5.1.1, 5.2, 5.2.1, and 5.2.2, Message "the heapsize limit for 'P' format has been reached. (such as the IXPE Level 1 event files) containing variable-lengthĪrrays may trigger in several IXPE tools a "ValueError" with the To fix this issue, update to version 3.7.0 (or newer).ĭue to a bug in certain 5.x versions of AstroPy, some files Unhelpful error message when using MatPlotLib older than versionģ.7.0. The IXPE task ixpeplot_polarization may fail with a cryptic and " punlearn fkeypar" and switch to using ftkeypar directly The fkeypar parameter file (~/pfiles/fkeypar.par) if fkeypar is used A bug in the new wrapper may cause corruption of To the task ftkeypar (which was designed to supplant fkeypar In HEASoft 6.32 the task fkeypar was replaced with a wrapper Missing operator at expression " eq "EQUATORIA."Ĭopy the new "ra_dec_to_pixel.tcl" into this folder (source code distribution only): Use of the ximage command ra_dec_to_pixel may result in % cd heasoft-6.32/ftools/xselect/xselflib/ To rebuild xselect and fix the problem, download that file and then:Ĭopy the new "xsel_bin.f" into this folder (source code distribution only): This appears to result from an uninitialized variable, and is addressed Nuproducts_0.3.3: Unable to copy file: '134999_bk.pha' in The source file: //xsel134999_histI.xsldoesn't exist. Some Ubuntu (and other?) Linux users may find that xselect causesĪ crash in e.g., nuproducts or other scripts, reporting messages % cd heasoft-6.32/asca/tasks/addascaspec/ Heasoft-6.32/ftools/asca/tasks/addascaspec/ To fix the problem, download that file and then:Ĭopy the new "addascaspec" into this folder (source code distribution only): Open file 'mathpha_expr': No such file or directory". When specifying both of the optional 'outbgd' and 'errmeth' parametersįor addascaspec, it fails with "Fortran runtime error: Cannot This issue may be mitigated by disabling "3D acceleration" in the display options. VirtualBox), FV windows may appear blank. Heasoft-6.32.1/Xspec/src/XSutil/Utils/TimeUtility.cxx Users should be able to get past this by editing lines 47-51 of 'timespec_get' was not declared in this scope
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |