Hotspot - kind of build and how to detect?

Mani Sarkar sadhak001 at gmail.com
Sat Feb 16 08:43:17 UTC 2013


Thanks David I will take it from here, I have found a couple of
work-arounds to the below.

Cheers,
mani

On Fri, Feb 15, 2013 at 2:16 PM, David Holmes <david.holmes at oracle.com>wrote:

> On 16/02/2013 12:09 AM, Mani Sarkar wrote:
>
>> I have written a bash script which looks for gamma, but gamma can be
>> created using different make parameters resulting in 'gamma' being
>> created in a nested folders (with various name combinations). I have
>> figured a way to locate gamma but it would be best to be able use the
>> data available to configure.
>>
>
> configure doesn't know where gamma will be. hotspot makefile make that
> decision.
>
>
>  With regards to your comment on make, is it not possible to write these
>> values once they are available (post build) into environment variables -
>> or as you saying we cannot write them into environment variables at all.
>>
>
> It is not the job of a Makefile to export environment variables back to
> the parent process.
>
> But you are free to modify the makefiles to expose this value of GAMMA for
> your own needs.
>
> David
>
>  Cheers,
>> mani
>>
>> On Fri, Feb 15, 2013 at 1:44 PM, David Holmes <david.holmes at oracle.com
>> <mailto:david.holmes at oracle.**com <david.holmes at oracle.com>>> wrote:
>>
>>     On 15/02/2013 9:42 PM, Mani Sarkar wrote:
>>
>>         Thanks David, I appreciate your help so far. I'm devising a way
>>         around
>>         the below you mentioned.
>>
>>         Would it be possible in future releases of your specs / scripts
>>         to echo
>>         these values (and other useful ones) out into the OS as
>> environment
>>         variables, it would defo help with utilities or scripts running
>>         around
>>         the OpenJDK program - similar to the one I'm working on atm.
>>
>>
>>     I'm not sure what you are suggesting. configure generates makefiles
>>     with make variables. It doesn't set environment variables - nor is
>>     there a way to do so. Many of the variables do not have a value
>>     until make is run during an actual build. So I really don't know
>>     what you are asking for.
>>
>>     David
>>
>>         Cheers,
>>         mani
>>
>>
>> --
>> *Twitter:* @theNeomatrix369
>> *Blog:* http://neomatrix369.wordpress.**com<http://neomatrix369.wordpress.com>
>> *JUG activity:* LJC Advocate
>> *Meet-a-Project:* https://github.com/**MutabilityDetector<https://github.com/MutabilityDetector>
>> *Come to Devoxx UK 2013:* http://www.devoxx.com/display/**UK13/Home<http://www.devoxx.com/display/UK13/Home>
>> */Don't chase success, rather aim for "Excellence", and success will
>> come chasing after you!/*
>>
>


-- 
*Twitter:* @theNeomatrix369
*Blog:* http://neomatrix369.wordpress.com
*JUG activity:* LJC Advocate
*Meet-a-Project:* https://github.com/MutabilityDetector
*Come to Devoxx UK 2013:* http://www.devoxx.com/display/UK13/Home
*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*



More information about the build-dev mailing list