From: Michael Snyder <msnyder@vmware.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: how much to regenerate
Date: Wed, 12 Nov 2008 18:55:00 -0000 [thread overview]
Message-ID: <491B2677.6070308@vmware.com> (raw)
In-Reply-To: <491AEC8C.80707@oarcorp.com>
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!
next prev parent reply other threads:[~2008-11-12 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 14:48 Joel Sherrill
2008-11-12 18:55 ` Michael Snyder [this message]
2008-11-12 22:07 ` Joel Sherrill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491B2677.6070308@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox