Closed kakirastern closed 4 years ago
I do not see this error when I compile on linux with gfortran 5.4. Which version of gfortran are you using? It could be that more recent versions apply the standard more strictly.
Hi @rwesson I am using gcc@9
installed with homebrew
. I tried something to the effect of
export FCFLAGS="-w -fallow-argument-mismatch"
export FFLAGS="-w -fallow-argument-mismatch"
and that seemed to have been able to suppress the errors, but now am seeing another error
ld: library not found for -lcfitsio
I am wondering if by chance you know where I can locate this cfitsio
library?
No worries, it is weird. I tried updating the CFITSIOFLAGS
path in the Makefile
, but that did not seem to have worked. So I tried using
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/local/lib
which did the trick.
Thanks for your help!
Finally, is there any reason why alfa
is writing all the outputs to a single FITS file's 3 different extensions FIT
, LINES
, and QC
instead of three separate files like it used to do? And, is there any way to change this?
Thanks for the extra information! I will try to update the code to compile properly with later GCC versions.
I changed the default output format to FITS starting from version 2.0, as it is much easier to handle within the code, and it avoids a problem where the output format can overflow, resulting in "***" instead of numbers in the text outputs. Text output is still available though - specify "--output-format text" in the command.
Ah, I see... Thanks for the info!
I've fixed this now (commit 5b1f1a2a0c4e93c619a209975e1a2809904c745a). The strict typing standards applied by the latest gfortran meant that I had to change some values from simple numbers to a single-valued array containing the number. I've verified successful compilation with gfortran versions 5.4, 9.3 and 10.01 now.
Thanks @rwesson Appreciate your message
While trying to run
make
on my MacBook Pro with gcc installed usingbrew
, I ran into some errors as follows:I would like to know if the issue is with the code, or if the issue is on the client side. Any help would be much appreciated.