IRAF on FC5 with ncl
mcba wrote on Aug 05, 2006
I'm trying to use ncl (SAO's "new" cl, which has command-line editing) with Fedora Core 5 and IRAF 2.12.2a-EXPORT.
When I run it I get PANIC "memory has been corrupted problems" when doing things like "imstat dev$pix".
I've tried recompiling ncl from the source (which incidentally required setting the XC_CC and XC_LINKER environment variables to gcc32, since the IRAF cl doesn't compile with version 4 gcc due to problems with varargs), but this hasn't helped.
Any ideas?
Cheers,
Michael Ashley / University of New South Wales
When I run it I get PANIC "memory has been corrupted problems" when doing things like "imstat dev$pix".
I've tried recompiling ncl from the source (which incidentally required setting the XC_CC and XC_LINKER environment variables to gcc32, since the IRAF cl doesn't compile with version 4 gcc due to problems with varargs), but this hasn't helped.
Any ideas?
Cheers,
Michael Ashley / University of New South Wales
Mike Fitzpatrick wrote on Aug 05, 2006
Hi Michael,
Note, the ECL (Enhanced CL) has the same cmdline editing capability as well as error handling. It is the standard CL for the V2.13-beta2 release from this site or as an add-on for earlier releases. I don't think NCL is still being supported, but that isn't part of the problem anyway.
Sounds like the 'stacksize problem' in V2.6 kernels. It could mean the iraf installation was updated with a source patch but the binaries are from an earlier version, check that they date from July '04 (i.e. "cl> dir bin$*.e long+"). The fix is to issue the command
limit stacksize unlimited (for c-shell users, or)
ulimit -s unlimited (for bash users)
The 'cl' command script should do this automatically, verify that hlib$cl.csh has the above 'limit' command in it. Otherwise, issue the command at the unix prompt before typing 'cl' and let me know if you still have problem.
Just FYI, the various gcc 4/varargs problems in the system are fixed in the V2.13 series. Hope this helps.
Cheers,
-Mike
I'm trying to use ncl (SAO's "new" cl, which has command-line editing) with Fedora Core 5 and IRAF 2.12.2a-EXPORT.
Note, the ECL (Enhanced CL) has the same cmdline editing capability as well as error handling. It is the standard CL for the V2.13-beta2 release from this site or as an add-on for earlier releases. I don't think NCL is still being supported, but that isn't part of the problem anyway.
When I run it I get PANIC "memory has been corrupted problems" when doing things like "imstat dev$pix".
Sounds like the 'stacksize problem' in V2.6 kernels. It could mean the iraf installation was updated with a source patch but the binaries are from an earlier version, check that they date from July '04 (i.e. "cl> dir bin$*.e long+"). The fix is to issue the command
limit stacksize unlimited (for c-shell users, or)
ulimit -s unlimited (for bash users)
The 'cl' command script should do this automatically, verify that hlib$cl.csh has the above 'limit' command in it. Otherwise, issue the command at the unix prompt before typing 'cl' and let me know if you still have problem.
I've tried recompiling ncl from the source (which incidentally required setting the XC_CC and XC_LINKER environment variables to gcc32, since the IRAF cl doesn't compile with version 4 gcc due to problems with varargs), but this hasn't helped.
Just FYI, the various gcc 4/varargs problems in the system are fixed in the V2.13 series. Hope this helps.
Cheers,
-Mike
mcba wrote on Aug 05, 2006
Hi Mike,
Thanks for your rapid and accurate reply.
Yep, that was it! I do have July '04 binaries, but the ncl script wasn't unlimiting the stack. Thanks for the pointer to ECL.
Cheers,
Michael
Thanks for your rapid and accurate reply.
fitz
Sounds like the 'stacksize problem' in V2.6 kernels. It could mean the iraf installation was updated with a source patch but the binaries are from an earlier version, check that they date from July '04 (i.e. "cl> dir bin$*.e long+"). The fix is to issue the command
limit stacksize unlimited (for c-shell users, or)
ulimit -s unlimited (for bash users)
Yep, that was it! I do have July '04 binaries, but the ncl script wasn't unlimiting the stack. Thanks for the pointer to ECL.
Cheers,
Michael
Last post on Aug 05, 2006