gpt-build accepts flavors, packages, and bundles for input and the builds all of the packages and bundles with all of the flavors. Each flavor is built in the same source directory of a package. To build the globus_common package you star with an empty $GLOBUS_LOCATION and run gpt-build gcc32 gcc32pthr globus_common-3.5.tar.gz. What you see is actually two packages being built with the two flavors. The globus_core package is used to install flavor specific files into $GLOBUS_LOCATION which are then used to help build the other packages. See this section for details. Here are some comments on the build output:
The following is a package removal message:
gpt-build ====> REMOVING empty package globus_core-gcc32-pgm_static
Each source package builds several binary packages types. However not all package types are built. In this case the package was built using dynamic linking which means that the static binary package is empty.
The following is noise that should be ignored. The make distclean command is needed to clean out a previous flavor. In this case there was no previous flavor.
make distclean make: *** No rule to make target `distclean'. Stop.