iraf.net

Howdy, I've just installed IRAF 2.12.2 with the patch-2a on a machine running Ubuntu with linux kernel 2.6.17-11. I'm trying to build the CTIO package from source, something i've done dozens of times on redhat systems, but the build fails. There are multiple compiler errors, the first of which is:t_mkshift.c:382: error: conflicting types for mkdela_
t_mkshift.c:248: error: previous declaration of mkdela_ was hereIf I had to hazard a guess, i'd say that the issue is gcc upgrading a major version from gcc-3.x to gcc-4.1.2. Whenever this happens, older code tends to not compile. Of course, I could be wrong (and probably am). any suggestions? thanks,
bri.

In this case the culprit is most likely starting at line 204 of fabry$t_mkshift.x:[code:1:0778984118]
# Compute deltas and sigmas
call salloc (work, nstars, TY_REAL) do i = 2, nimages {
call mkdelta (i, nstars, nimages, Memi[index+i-1], Memr[x_table],
dx[i], sigx[i], work)
call mkdelta (i, nstars, nimages, Memi[index+i-1], Memr[y_table],
dy[i], sigy[i], work)
}
[/code:1:0778984118]The mkdelta() procedure is declared such that 'work' is a real array, but it is being passed in as an int pointer. Change the calls to 'Memr[work]' instead and you can start working through the next problem.The newer GCC compilers get pickier as they get older (as do I), you may find other type problems that used to be legal. Most often these will be boolean/int type clashes (e.g. an int variable used as a boolean in an if-clause, checked against TRUE/FALSE instead of YES/NO, etc. Cheers,
-Mike

Heya Mike, are there any plans to update the code to make it gcc-4.x compatible? I'm not sure who supports that particular package.But you're right, I'll likely find problems with lots of packages. I can install a concurrent installation of gcc-3.<latest version>. What's the procedure for changing which compiler xc calls?thanks!bri.

All the packages available from this site have already been updated to compile for at least the 4.0 compiler (had to for the macintel systems). CTIO has been an orphaned package for quite a while but we can do what's needed to keep it running, and will continue to do so. It looks like gcc 4.1 will bring new problems so I'll pay attention to that next time I build all the packages, otherwise if you can't get it to build then using the pre-built binaries will (usually) always work.-Mike