x11iraf under RHEL WS4, 64-bit
Ed Anderson wrote on Jun 20, 2006
Hi
I'm having a rough time trying to compile X11IRAF under Redhat WS 4 (64-bit).
Any comments, suggestions would be greatly appreciated.
Thanks,
-- Ed
I'm having a rough time trying to compile X11IRAF under Redhat WS 4 (64-bit).
Any comments, suggestions would be greatly appreciated.
Thanks,
-- Ed
Mike Fitzpatrick wrote on Jun 20, 2006
Hi Ed,
Try building the sources from
http://iraf.net/ftp/pub/fitz/x11iraf-new_gcc.tgz
The list of X11IRAF work is reaching critical mass but if you could be more specific about what problems you're having I might have suggestions. Note I haven't tried any of this as 64-bit, you might want to just use 32-bit binaries if there are problems.
Cheers,
-Mike
Try building the sources from
http://iraf.net/ftp/pub/fitz/x11iraf-new_gcc.tgz
The list of X11IRAF work is reaching critical mass but if you could be more specific about what problems you're having I might have suggestions. Note I haven't tried any of this as 64-bit, you might want to just use 32-bit binaries if there are problems.
Cheers,
-Mike
Ed Anderson wrote on Jun 20, 2006
Hi Mike,
I tried the 32-bit binary ... at first I got an error about not having
libtermcap.so.2 . It turned out that the 32-bit compatibility libraries were not
installed.
Now that I have libtermcap there, the next error is:
iraf@orion.phy.nau.edu% ./xgterm
xgterm: no available ptys
Any ideas?
Cheers,
-- Ed
I tried the 32-bit binary ... at first I got an error about not having
libtermcap.so.2 . It turned out that the 32-bit compatibility libraries were not
installed.
Now that I have libtermcap there, the next error is:
iraf@orion.phy.nau.edu% ./xgterm
xgterm: no available ptys
Any ideas?
Cheers,
-- Ed
Mike Fitzpatrick wrote on Jun 20, 2006
Hi Ed,
Sorry I've been dragging my feet on this. The pty error is fixed using the special Fedora-had-to-go-and-break-everything binary from
http://iraf.net/ftp/pub/fitz/xgterm.fedora
Cheers,
-Mike
Sorry I've been dragging my feet on this. The pty error is fixed using the special Fedora-had-to-go-and-break-everything binary from
http://iraf.net/ftp/pub/fitz/xgterm.fedora
Cheers,
-Mike
Ed Anderson wrote on Jun 20, 2006
Thanks Miike,
I'm gettting closer ... now it wants libncurses.
But up2date --arch=i386 libncurses claims that there is no such package.
Do you know which package this library is in?
-- Ed
I'm gettting closer ... now it wants libncurses.
But up2date --arch=i386 libncurses claims that there is no such package.
Do you know which package this library is in?
-- Ed
Mike Fitzpatrick wrote on Jun 20, 2006
Try 'ncurses', on some systems I think it is in the 'termcap' or 'terminfo' packages.
-Mike
-Mike
Ed Anderson wrote on Jun 20, 2006
Situation resolved.
For the sake of anyone running RedHat.
To figure out what package is associated with a given file, use rpm -qf filename
On the 64-bit machines, where one needs the 32-bit support, you can then
get the 32-bit packages with: up2date --arch=i386 <packagename>
-- Ed
For the sake of anyone running RedHat.
To figure out what package is associated with a given file, use rpm -qf filename
On the 64-bit machines, where one needs the 32-bit support, you can then
get the 32-bit packages with: up2date --arch=i386 <packagename>
-- Ed
Last post on Jun 20, 2006