This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documenting tools necessary for GCC [draft]
- From: Andreas Schwab <schwab at suse dot de>
- To: Phil Edwards <phil at jaj dot com>
- Cc: Dan Kegel <dkegel at ixiacom dot com>, gcc at gcc dot gnu dot org,ghazi at caip dot rutgers dot edu
- Date: Tue, 03 Jun 2003 18:05:13 +0200
- Subject: Re: Documenting tools necessary for GCC [draft]
- References: <3EDB9C16.3070704@ixiacom.com><20030602185455.GA21600@disaster.jaj.com>
Phil Edwards <phil@jaj.com> writes:
|> On Mon, Jun 02, 2003 at 11:48:54AM -0700, Dan Kegel wrote:
|> >
|> > Also, can you address whether and how to regenerate */aclocal.m4?
|> > I have a feeling those are hand-generated only now, and
|> > using any version of automake's aclocal command to generate them
|> > is an error, but I don't have evidence to back this up.
|>
|> Not exactly.
|>
|> if <an acinclude.m4 file exists>
|> then
|> <automake is being used; use aclocal(1) to generate aclocal.m4,
|> which will contain acinclude.m4 plus things needed by automake>
acinclude.m4 is not a prerequisite for automake, aclocal also collects
macros from all *.m4 files that it find in its search path.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."