Posted: Wed Dec 01, 2010 2:06 pm Post subject: Install/Update packages Ubuntu 32bit Virtual Machine
Hi
I've managed to install v2.15 on a Ubuntu Virtual Machine running on Mac OSX 10.6. The only error I encountered was resolved by creating the symbolic link as described here:
The main reason I installed IRAF on the VM is just to check if everything is fine, before I switch my Mac installation to the latest version.
One thing remains: When I follow the instructions on how to install new packages, I get an error:
when I run .configure as instructed in the documetation, a Makefile is created. Executing the Makefile results in errors:
sudo make check yields this:
Updating repository data ....
iraf: Undefined variable.
iraf: Undefined variable.
cat: .repo_manifest: No such file or directory
cat: .repo_manifest: No such file or directory
The same for make update:
Updating repository data ....
iraf: Undefined variable.
iraf: Undefined variable.
cat: .repo_manifest: No such file or directory
cat: .repo_manifest: No such file or directory
?
Last edited by AnTaR3s on Wed Dec 01, 2010 9:55 pm; edited 1 time in total
Ooops. It appears one of the scripts sets a path based on $iraf which shouldn't be there. You can either define a $iraf variable to be the iraf root directory, or else do a
Code:
make self_update
and get the latest installation scripts to fix this, then try installing the package again.
I saw that error in both Fedora 14 and during an install under Ubuntu (on my home machine late last night...) and fixed it by setting the $iraf variable to /iraf/iraf. I did have to install the csh package and change user iraf to use /bin/csh since the csh package is not part of the default Ubuntu (10.10) install.
One question for Fitz: Does it matter if I run the extern package updates, installs, etc. as user iraf or root? It seems to work both ways. I ran the ./configure as both and they both seemed to work, but I'm waiting for some subtle "feature" to show itself somewhere down the line. Since it seemed to work fine as user iraf, I ran all the make calls as iraf when I installed a few external packages and it seems fine (crossing my fingers..).
Does it matter if I run the extern package updates, installs, etc. as user iraf or root? It seems to work both ways.
The only requirement is that you are able to write to the iraf$extern directory. Installing as root is fine but keep in mind the files may then be owned by root, and updates done later as 'iraf' will see a permissions problem. You can change the iraf tree to all be owned by the same iraf user with a command such as
Code:
% sudo chmod -R iraf:users $iraf
The need for an 'iraf' user at all will go away shortly (just didn't have time to make it into this release).
Hmmm...
I defined the $iraf (/iraf/iraf/ which is iraf root) variable before running the install script, both in csh and bash...
the make self-update results in the same error...
The difference to jscotti's install is, that I didn't create an iraf-user in the first place, I installed everything as root...
Do you mean the command itself fails, or after doing the self_update the command still fails? I see now where the 'make self_update' actually uses the script that needs to be fixed by installing the update! Duh.
In any case, defining a $iraf in your environment before the update should fix it. Otherwise, manually edit the $iraf/util/pkgget script and remove the use of '$iraf' in the 'set path = ...." command and try again.
Now that I've seen the impressive updates of IRAF 2.15 I moved my main system to the latest version.
I run Mac OS 10.6.5 and boot into the 64bit kernel.
What I did (just in case anyone looks for that):
moved my old iraf tree (/iraf/iraf/) to a backup location and unpacked the new distro there (downloaded the 32/64bit combo).
the old login.cl started the new version right away, but the error I described above occurred in Mac OSX as well, althouh the $iraf variable is also definitely set (I guess I'm doing something wrong...)
At last I merged my modified data (imdirs, graphcap, imtoolrc, obsdb.dat) into the new installation.
I hope the system will also work when I boot into the 32bit mode...
Posted: Fri Jan 07, 2011 9:16 pm Post subject: Cannot Update External Packages
Hi, I am trying to install Iraf v2.15 on Fedora14. I am new to this and cannot get the external packages to configure. I tried defining $iraf to be /iraf/iraf/, but keep getting the following error messages:
liza> ./configure
Initializing repository data ....
cat: .repo_manifest: No such file or directory
cat: .repo_manifest: No such file or directory
Creating system makefile ....
Setup Complete.
and
liza> make self_update
Updating repository data ....
cat: .repo_manifest: No such file or directory
cat: .repo_manifest: No such file or directory
tar (child): /tmp/util.tgz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
I have encountered a problem today when I wanted to update my Macbook installation (I know this topic is about Ubuntu, but I didn't want to open a new topic...). I installed the patch to v2.15.1 as instructed which worked perfectly, but when I did a make check I got this:
Updating repository data ....
Package adccdrom is not installed ....
Package cfh12k is not installed ....
ls: No match.
Package deitab is not installed ....
ls: No match.
ls: No match.
Package gemini is not installed ....
Package gmisc is current ....
ls: No match.
Package iue is not installed ....
Package mem0 is not installed ....
Package mscdb is not installed ....
ls: No match.
ls: No match.
Package nfextern is not installed ....
ls: No match.
Package rvsao is not installed ....
Package song is not installed ....
Package sqiid is not installed ....
Package stecf is not installed ....
Package steward is not installed ....
ls: No match.
ls: No match.
Package ucsclris is not installed ....
Package upsqiid is not installed ....
Package xdimsum is not installed ....
sudo make update results in the same error. I'm 95% sure this error occurred also before the update to 2.15.1. The strange thing is that it works on my iMac...any clue?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum