Yes.  You have to do a 

$GLOBUS_LOCATION/sbin/globus-build -force globus_core*.tar.gz <flavor>

first.  That will create libexec/globus-build-env-<flavor>.sh

Just grab globus_core-2.1.tar.gz from
ftp://ftp.globus.org/pub/gt2/2.0/packages/src/

Yes.  I just want to keep tabs on this so I know when I don't have to tell that
to people (for the simpleCA) anymore.

*** Bug 174 has been marked as a duplicate of this bug. ***

The upcoming release of GPT2.2 includes globus_core as part of the GPT.  Thus,
when binary SDKs are used with GPT2.2, this should no longer be an issue. 
GPT1.x will most likely never be updated to deal with this issue.

>The upcoming release of GPT2.2 includes globus_core as part of the 
>GPT.  Thus, when binary SDKs are used with GPT2.2, this should no longer 
>be an issue. GPT1.x will most likely never be updated to deal with this issue.

Are you mixing GPT and GT, or am I confused? I don't know how putting 
globus_core into GPT would change things, but putting it into GT 2.2 would 
fix things.

Do you mean that GT2.0 will not be updated?

Thanks for keeping me up to date.

-alain

The issue is that we can't really deliver binary packages of globus_core,
because most of what is in globus_core is locations of things that have been
discovered on the local system.  The solution for the future is that as of GPT
(and yes, I mean GPT, the packaging tools) version 2.2, the source of
globus_core will be included with GPT2.2, so that it can be built in whatever
flavor is needed.

If using versions of GPT less than 2.2, you will need to get a source tarball of
globus_core, and build it for the flavor you wish to use.  Then the binary SDKs
should work for you.

Using the GPT2.2 (Which has not yet been released) with binary SDKs from the
Globus Toolkit v 2.0 should work, as will compiling globus_core from source
(using any version of the GPT).