Hi Charles,
Thank you for the clarification. I now managed to work around
building Globus from source by installing Globus-Base-SDK via VDT (as
recommended by you) and building glite.security.voms from source in
order to get the necessary libraries for the MyProxy build.
Thank you very much for your help, appreciated.
Cheers,
Florian.
On 31 Oct 2007, at 15:23, Charles Bacon wrote:
On Oct 31, 2007, at 10:05 AM, Florian Scharinger wrote:
I'm getting my errors when building globus from source. Hence I
thought that would be the appropriate list. But I'm happy to be
convinced otherwise.
So, the real issue you're seeing is this:
1) Binary GPT packages have many different types, including pgm
(programs), rtl (libraries), dev (headers), doc (documentation) and
others.
2) VDT doesn't install all of the types of binary packages. For
instance, it will tend to exclude dev packages as being unnecessary
to runtime operation.
3) Our source installer is seeing that packages are already
installed, so gives "SKIPPING REBUILD" even though one of the
package types (-dev) is missing. This is because GPT doesn't know
ahead of time what kinds of binary packages will come out of a
source package
The issue is therefore Globus's to deal with, and this forum is the
right one for that. However, problem (3) seems pretty hard to
solve. Installing the VDT's SDK package to pick up your missing -
dev packages seems like a good way to solve your problem. The
other workaround to point (3) would be to specify --with-
buildopts="--force" to force the build of those packages. You
might not want that, though, if VDT has patched some of those
packages.
The "build myproxy first" would also work with the force trick.
Build myproxy first, install VDT over the top of that to get VOMS,
then rebuild only the myproxy package using the -force option.
Charles
/ - - - - - - - - - - - - - - - - - - - - - - \
Florian Scharinger
EPCC
University of Edinburgh
EGEE-II SA1 NPM Developer
