Re: RPMMakefile fails after starting Makefile.Release target: create_ProductVersionFile

> For instance, when do you use the env_var_Linux.status  versus the
env_var.status file. Since the $PEGASUS_ROOT/Makefile is called by the
$PEGASUS_ROOT/rpm/RPMMakefile  and the Makefile uses
> env_var.status  and RPMMakefile  uses env_var_Linux.status , how do you
know which file has which setting for PEGASUS_ROOT . And how does one deal
with the build recommendations to have
> PEGASUS_ROOT set in the environment.

Most of the times env_var_Linux.status file is used for release builds and
env_var.status is used for development build. env_var_Linux.status file
will be included only when you defined PEGASUS_ENVVAR_FILE varaible
otherwise env_var.status file will be included.


Regards
Surendra




                                                                           
             John Robinson                                                 
             <[email protected]                                             
             m>                                                         To 
                                       Surendra Kodali/India/IBM@IBMIN     
             04/03/2010 19:55                                           cc 
                                       Paul von Behren                     
                                       <[email protected]>,         
                                       "[email protected]"         
                                       <[email protected]>,        
                                       "Sampige, Sahana Prabhakar (STSD)"  
                                       <[email protected]>                     
                                                                   Subject 
                                       Re: RPMMakefile fails after         
                                       starting Makefile.Release target:   
                                       create_ProductVersionFile           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Surendra,
Thanks for the info. It seems to explain why my attempt to execute: "make
-f pegasus/rpm/RPMMakefile buildRPM" did not work.
Apparently my setting of PEGASUS_ROOT in .bashrc overrode the setting used
in RPMMakefile and the associated build files.

I think I probably also mucked things up more by setting the value of
PEGASUS_ROOT inside of env_var_Linux.status.

So as to facilitate getting it right. Does someone have a step by step
cookbook for how to get a build done correctly.

For instance, when do you use the env_var_Linux.status  versus the
env_var.status file. Since the $PEGASUS_ROOT/Makefile is called by the
$PEGASUS_ROOT/rpm/RPMMakefile  and the Makefile uses env_var.status  and
RPMMakefile  uses env_var_Linux.status , how do you know which file has
which setting for PEGASUS_ROOT . And how does one deal with the build
recommendations to have PEGASUS_ROOT set in the environment.


Shouldn't one use a more sophisticated build tool such as SCons to handle
these various "environment" contexts in a rational fashion.

On Thu, Mar 4, 2010 at 3:01 AM, Surendra Kodali <[email protected]
> wrote:
  Pegasus RPMMakefile looks in env_var_Linux.status file for environment
  variables. Environment variables defined in .bashrc file will override
  the
  environment variables defined in env_var_Linux.status file. PEGASUS_ROOT
  specified in the env_var_Linux.status should be the rpm BUILD location
  NOT
  the pegasus src code in your local directory. For suppose if you are
  building rpms with root access on RHEL, PEGASUS_ROOT specified in the
  env_var_Linux.status should be "/usr/src/redhat/BUILD/tog-pegasus-2.9.1"
  otherwise simply comment all the below env varibles in
  env_var_Linux.status
  file.

  #PEGASUS_ROOT=
  #PEGASUS_HOME=
  #PEGASUS_PLATFORM=

  Pegasus rpm spec file will take care of all the above mentioned
  environment
  variables.

  Regards
  Surendra