General FAQ

1. Which module should I check out from the CVS repository.

We encourage you to checkout one of the "-all" (e.g., IRISNET-all, OA-all etc.) modules, since it comes with all the necessary packages. Thus you are less likely to have any installation problem.

2. I have a few of the 3rd party packages used by IrisNet already installed in my computer. Should I still checkout the "-all" modules, which come with the same packages I have?

If you do not have space limitation in your hard disk, we recommend you to checkout the "-all" modules. Otherwise, the installation scripts (e.g., install, configure, Makefile) may not find the correct paths to your already installed packages. If you do not checkput a required package, and instead intend to use your already installed package, you may need to manually modify the installation scripts so that they find your package. We tried to minimize this effort as best as possible, so the installaiton scripts should automatically find the already installed packages. If you have such problems, please mail us at irisdev@intel-iris.net.

Note that, even if you checkout the "-all" modules and install all the required 3rd party packages, they will not interfere with your already installed packages. IrisNet installs everything under the installaiton directory.

3. I tried to checkout the IrisNet code from the CVS repository, following the instructions in the download page. But the chekout failed. Why?

This should not happen if the machine iris.wv.cc.cmu.edu is online. If you still face the problem, inform us.

4. How do I know when there is any update of the IrisNet code? (Or, how do I know when I should do a cvs update?)

Subscribe to the list iris-announce@intel-iris.net, by sending a request mail to majordomo@intel-iris.net. The body of the request mail should contain the line "subscribe iris-announce". For more informations about the mailing lists, visit this page.

Specific Package Related FAQs

OpenCV

1. I tried to install the OpenCV that comes with the IrisNet code. But I get conifuguration error. What can be wrong?

We have been reported of a few instances of this problem, and in all the cases the problem was due to the absence of a compatible Tcl/Tk package. OpenCV requites Tcl/Tk version 8.3 or later, so if your computed does not have Tcl/Tk 8.3 or later vesion installed, you might get this configuraiton error.

We have tried to tweak the OpenCV configure script so that in case Tcl/Tk is not installed in your computer, OpenCV uses the one that comes with IrisNet. Now, you should not get this Tcl/Tk related configuration errors. If you still do, please mail us at irisdev@intel-iris.net. And, as a quick fix, install Tcl/Tk 8.3 in your computer. :)

CamStream

1. CamSteam configuration failed with the message: checking for Qt library version >= 2.2.0... no. What can I do?

Download and install the latest QT package :).

2. I have the QT package installedm and its version is higher that 2.2.0. But I still get the above message. What should Ido?

Set the enviroment variable QTDIR to the QT directory path.

3. I have downloaded the latest stable release of IrisNet. However, when I run the install script, I get the error message "*** Camstream build failed ***", although all other packages are installed successfully. What is wrong?

If all the modules except Camstream are compiled successfully, then one possible reasons for getting the above mentioned error message is that you are using gcc3.2 for compiling the packages. Some portion of the specific version of Camstream we use cannot be compiled with gcc3.2, which accounts for this error message. Fortunately, the camstream libraries critical to IrisNet are compiled successfully with gcc3.2 (this is the reason all other IrisNet modules are installed successfully).

You can ignore the error message, since all other components of IrisNet has been installed successfully. Alternatively, you can install gcc 2.95, and use that to compile the whole IrisNet package.

If you have any other installation problems, mail them to irisdev@intel-iris.net. We will either fix those problems in future releases or include them in this FAQ page.