Yes. If you know the name of the package you depend on, you can run:
$ gpt-query <package_name>
For example:
$ gpt-query globus_openssl
9 packages were found in /Users/bacon/pkgs/globus-4.0.6 that matched
your query:
packages found that matched your query
globus_openssl-gcc32-dev pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32-pgm pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32-rtl pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32dbg-dev pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32dbg-rtl pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32dbgpthr-dev pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32dbgpthr-rtl pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32pthr-dev pkg version: 1.20.0 software
version: 0.9.7d
globus_openssl-gcc32pthr-rtl pkg version: 1.20.0 software
version: 0.9.7d
You can parse the flavor out of that. I've done that like this before:
export FLAVORS=`$GLOBUS_LOCATION/sbin/gpt-query -
name=globus_gsi_sysconfig -pkgtype=rtl | grep sysconfig | awk -F-
'{print $2}'`
If you need to know what headers/libraries to link against, you can
use globus-makefile-header:
$ globus-makefile-header --flavor=gcc32dbg globus_openssl
That requires that globus_core was also built for that flavor, which
won't be true in a binary installation. That is to say, in a binary
installation we don't know where the compiler lives on that machine,
we only knew where the compiler was when we built the binaries. So
in a binary installation you want to run:
$ gpt-build -nosrc gcc32dbg
to build the built-in globus_core package. Then globus-makefile-
header will say something like:
GLOBUS_OPENSSL_VERSION = 1.20.0
GLOBUS_CFLAGS = -g -fno-common -Wall
GLOBUS_INCLUDES = -I/Users/bacon/pkgs/globus-4.0.6/include/gcc32dbg
GLOBUS_LIBS =
GLOBUS_LDFLAGS = -L/Users/bacon/pkgs/globus-4.0.6/lib -L/Users/bacon/
pkgs/globus-4.0.6/lib -L/sw/lib
GLOBUS_PKG_LIBS = -lssl_gcc32dbg -lcrypto_gcc32dbg
[...]
The quick&dirty way to do it is to look under $GLOBUS_LOCATION/etc/
gpt/packages/<package_name> for the corresponding
pkg_data_<flavor>_<pkgtype>.gpt files.
Charles
On Jan 23, 2008, at 12:50 PM, Edward Maros wrote:
I am working on a 3rd party package that needs to know the flavor
used when compiling gt 4.0.5. Is this information available post
installation?
Thanks,
Ed
