Re: please resend your googoogaga msg -- Re: Trouble building goo-0_0140

[James Knight <jknight@xxxxxxxx>]

On Friday, August 2, 2002, at 12:29  PM, Neel Krishnaswami wrote:
> Andrew Sutherland writes:
>>
>>> From the wiki (http://www.ai.mit.edu/~jrb/goo/wiki/index.php/GooFs)
>> ---
>>
>> When I attempt to load a file, define a method, or otherwise invoke
>> dynamic compilation, I am given a gcc error about being unable to find
>> "grt.h" and/or "dlgrt.h"
>>
>> Environment troubles again. Make sure that you have both GOO_ROOT and
>> GOO_BUILD_ROOT set, especially whenever you build goo using make, as
>> it will steal those environment variables and use them as defaults.
>>
>> Alternatively, make sure that what Goo thinks is GOO_ROOT has either a
>>
>>     * validly populated lib sub-directory
>>     * sym-link from lib to the c directory
>>
>> The reason for this is that when dynamically compiling stuff, Goo does
>> an -I of GOO_ROOT/lib (where GOO_ROOT is nabbed from the environment,
>> or falls back on what was compiled in.)
>
> My GOO_ROOT is /tmp/goo, but I'm still getting the error. But I find
> the various *.h files all live in GOO_ROOT/lib/goo/lib -- is this a
> problem? If so, how do I fix it?
>
> Do I need to set GOO_BUILD_ROOT/GOO_ROOT before running configure? I
> thought --prefix=/tmp/goo would do the trick?

If you use configure --prefix=/tmp/goo it should set the default 
GOO_ROOT to /tmp/goo/lib/goo. Then it will search for the .h files in 
/tmp/goo/lib/goo/lib, which should be fine. Are you not seeing that 
behavior?

The sentence above about setting the env var during 'make' is outdated. 
It has been superseded by the use of configure --prefix.

James