External Products

In addition to the D0 code itself, many "external" products are needed in order to build and/or run many of the executables. We can't give you a list of the products needed in this document, they change too quickly and we can't know what subset of the executables you need at your site.

But we can and have supplied some tools which make it possible to determine what you need.

First a little background:

When you "setup D0RunII ..." you setup a lot more than just that one product. D0RunII sets up, or can setup all of the "internal", the source code packages, and "external" packages. The "internal" ones are all "required". The "external" are almost all "optional". The latter means that if that package isn't present on your system, the setup won't complain. This is done because it should not be necessary for you to install external products, especially proprietary ones which cost money, that you will never use. Since we can't know in enough detail what is used by what executable or what your needs are, we've made them all optional (mostly).

In addition, we always setup specific versions of everything. Sometimes this isn't needed. But it's the only way that we can be sure that results obtained at different sites will be consistent.

What external products/versions do you need?

Once you have a version of D0RunII installed, you should be able to "setup D0RunII <version>". The command "D0-glpkgs-chk.sh" will check to see if you have installed each of the external packages that might be used by that version of D0RunII. The output will look like:

>> D0-glpkgs-chk.sh
**** OK whod0 v1_0   
**** OK kai v4_0f   
**** OK TestData v00-01-20   
**** OK python v2_1a   
**** OK python v2_1   
????    swig v1_1p5a   
**** OK swig v1_1p5   
**** OK gtools v2_3   
. . .

Products marked by "**** OK" are installed. Those marked by "????" aren't.
NOTE: some of them, such as "python" and "swig" above have more than one entry. This is normally because there are different versions needed on different operating systems, Linux/Irix for example. You'll only need one of them. Sometimes though, "python" above, both versions exist. In this case the first one listed will be the one actually used.

How do I install them?

Unfortunately there isn't any really easy way to install all of these, even the first time, since we don't know what you want/need. The right way is to understand what they are and do so you can decide what you need then download them one by one from whichever distribution site has them. Give that that won't happen the easy way might be something like:

cut and paste the list from D0-glpkgs-chk.sh to a file.
edit the file, removing products you know you don't need and any that you already have.
change "???? " to "upd install -h www-d0.fnal.gov "
setup upd
source the file you just created, pipe/tee or just redirect the output to a file.

This will install any products that exist on D0's distribution node. Check the log file for errors. There should be many products that it couldn't find. That's OK, you aren't done. But you may also see products that it tried to install but failed. You'll need to fix whatever problem caused those and redo the installs. ALSO look carefully for special instructions.

Repeat the above but this time do not include "-h www-d0.fnal.gov". This will install anything that's on FNKITS, Fermilab's product distribution node. Again, check for errors and special instructions. Especially at this step, some products need to have an "install as root" performed, others need licenses installed, etc.

Do D0-glpkgs-chk.sh one more time. If at this point there are packages that you think you need and you haven't installed them, contact us.

Comments, complaints, bug reports to:

Alan M. Jonckheere

Last modified: Mon Jan 14 10:45:06 CST 2002