how much to regenerate

how much to regenerate

[Joel Sherrill]

Hi,

I have a patch to sim/common/aclocal.m4 which
I need to commit after regenerating the proper
files.

http://sourceware.org/ml/gdb-patches/2008-11/msg00133.html

Do I just run autoconf in the common subdirectory
or is this included elsewhere?  If so, what is the
proper procedure for regenerating everything?

Thanks.

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985

Re: how much to regenerate

[Michael Snyder]

Joel Sherrill wrote:
> Hi,
> 
> I have a patch to sim/common/aclocal.m4 which
> I need to commit after regenerating the proper
> files.
> 
> http://sourceware.org/ml/gdb-patches/2008-11/msg00133.html
> 
> Do I just run autoconf in the common subdirectory
> or is this included elsewhere?  If so, what is the
> proper procedure for regenerating everything?

Yes, run autoconf, preferably only in the directory affected.
Make sure to use the same version of autoconf that was last
used in that directory, which you can find by looking at
"configure" (in this case, version 2.59), unless otherwise
noted (eg. by a collective decision to go to a later version).

See the example in sim/common/ChangeLog:

2008-07-11  Hans-Peter Nilsson  <hp@axis.com>

         * common.m4: Add test for libz and zlib.h.
         * configure: Regenerate to track ../common/common.m4 changes.
         * config.in: Ditto.

Thanks for asking!

Re: how much to regenerate

[Joel Sherrill]

Michael Snyder wrote:
> Joel Sherrill wrote:
>   
>> Hi,
>>
>> I have a patch to sim/common/aclocal.m4 which
>> I need to commit after regenerating the proper
>> files.
>>
>> http://sourceware.org/ml/gdb-patches/2008-11/msg00133.html
>>
>> Do I just run autoconf in the common subdirectory
>> or is this included elsewhere?  If so, what is the
>> proper procedure for regenerating everything?
>>     
>
> Yes, run autoconf, preferably only in the directory affected.
> Make sure to use the same version of autoconf that was last
> used in that directory, which you can find by looking at
> "configure" (in this case, version 2.59), unless otherwise
> noted (eg. by a collective decision to go to a later version).
>
>   
OK.  Thanks. I was worried since this was in "common".
I ran autoconf 2.59 but since this was just quoting
configure did not actually change. 

It is committed now.  Hopefully it did not break
anything but if it did, I am sure someone will
let me know. :)
> See the example in sim/common/ChangeLog:
>
> 2008-07-11  Hans-Peter Nilsson  <hp@axis.com>
>
>          * common.m4: Add test for libz and zlib.h.
>          * configure: Regenerate to track ../common/common.m4 changes.
>          * config.in: Ditto.
>
> Thanks for asking!
>
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985