euv1.9 and Iraf 2.14.1
JorgeS wrote on Oct 09, 2008
Hi,
I am trying to install euv1.9 with iraf 2.14.1 with no success so far.
I have Debian 4.0 (etch), and I could install Iraf 2.14.1 and Tables 3.8 smoothly.
However euv1.9 (external package) is giving me a lot of problems. That software (euv) has not been modified since 2000, so I guess it has to do with the C libraries, the C compiler, or something like that.
The error comes during compilation, when it tries to compile "libeox.a". In particular the piece of text is this:
...
xc -c -w -p euv eoxoptimal.x eoxout.x eoxprofile.x
eoxoptimal.x:
eox_optimal:
simp_dvzero:
eoxout.x:
eox_out:
simp_rterr:
eoxprofile.x:
eox_gprofs:
eox_gprof:
eoxoptimal.f:
eoxopl:
simpdo:
eoxoptimal.c:142: error: conflicting types for âsimpdo_â
eoxoptimal.c:66: error: previous declaration of âsimpdo_â was here
...
Then there are problems in several other libraries, but it is always a similar message. Any suggestion? Has anybody seen this problem before?
Jorge
I am trying to install euv1.9 with iraf 2.14.1 with no success so far.
I have Debian 4.0 (etch), and I could install Iraf 2.14.1 and Tables 3.8 smoothly.
However euv1.9 (external package) is giving me a lot of problems. That software (euv) has not been modified since 2000, so I guess it has to do with the C libraries, the C compiler, or something like that.
The error comes during compilation, when it tries to compile "libeox.a". In particular the piece of text is this:
...
xc -c -w -p euv eoxoptimal.x eoxout.x eoxprofile.x
eoxoptimal.x:
eox_optimal:
simp_dvzero:
eoxout.x:
eox_out:
simp_rterr:
eoxprofile.x:
eox_gprofs:
eox_gprof:
eoxoptimal.f:
eoxopl:
simpdo:
eoxoptimal.c:142: error: conflicting types for âsimpdo_â
eoxoptimal.c:66: error: previous declaration of âsimpdo_â was here
...
Then there are problems in several other libraries, but it is always a similar message. Any suggestion? Has anybody seen this problem before?
Jorge
Mike Fitzpatrick wrote on Oct 09, 2008
The problem has to do with how newer compilers are now dealing with functions declared as 'extern' but which appear in the same source file. In any case, I've put modified source and prebuilt binaries for the package in the download area (i.e. http://iraf.net/ftp/iraf/extern/ ). You can pick up the new source and build locally of else just install the binaries, beyond this the package has been pretty frozen for a while.
-Mike
-Mike
JorgeS wrote on Oct 09, 2008
Thanks Mike!
Yes, now it seems to work well. Thanks a lot!
Now I have a "next stop" on the way... PROS. I tried to install PROS 2.5, another external package quite related to euv. This package is frozen since 1999 too, and it fails when I try to install it too.
Is there any patch or newer files around?
Jorge
Yes, now it seems to work well. Thanks a lot!
Now I have a "next stop" on the way... PROS. I tried to install PROS 2.5, another external package quite related to euv. This package is frozen since 1999 too, and it fails when I try to install it too.
Is there any patch or newer files around?
Jorge
fitz
The problem has to do with how newer compilers are now dealing with functions declared as 'extern' but which appear in the same source file. In any case, I've put modified source and prebuilt binaries for the package in the download area (i.e. http://iraf.net/ftp/iraf/extern/ ). You can pick up the new source and build locally of else just install the binaries, beyond this the package has been pretty frozen for a while.
-Mike
Mike Fitzpatrick wrote on Oct 09, 2008
I put patched source and binaries in the same extern directory (see "pros_2.5.1-*.tar.gz").
As I remember it, there were a number of Y2K changes never applied to this package (it was frozen well before), just be aware of strange results or error messages.
-Mike
As I remember it, there were a number of Y2K changes never applied to this package (it was frozen well before), just be aware of strange results or error messages.
-Mike
JorgeS wrote on Oct 09, 2008
Great! Thanks again Mike!
It works now very well apparently. The data I will use is previous to 2000, but anyway I will keep an eye on possible Y2K issues... I can always change the date of the system ;-)
Thanks!
It works now very well apparently. The data I will use is previous to 2000, but anyway I will keep an eye on possible Y2K issues... I can always change the date of the system ;-)
Thanks!
Last post on Oct 09, 2008