This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: I run autoconf and get an empty file for "configure"

From: Tom Tromey <tromey at redhat dot com>
To: Adam Megacz <patches at lists dot megacz dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: 10 Feb 2002 18:22:23 -0700
Subject: Re: I run autoconf and get an empty file for "configure"
References: <Pine.LNX.4.10.10202101118090.6855-100000@mars.deadcafe.org> <86heoovprm.fsf@megacz.com>
Reply-to: tromey at redhat dot com

>>>>> "Adam" == Adam Megacz <patches@lists.megacz.com> writes:

>> Neither configure nor configure.in in the toplevel directory are generated
>> scripts. Both are maintained by hand.

Adam> If I make changes to Makefile.in, do I need to change
Adam> configure/configure.in, or will the changes get absorbed
Adam> automatically?

In the top-level directory, you just edit the files.  configure,
configure.in, and Makefile.in there are all hand-maintained.
Other directories typically use autoconf and, in some cases, automake.

Tom

References:
- Re: I run autoconf and get an empty file for "configure"
  - From: Jeff Sturm
- Re: I run autoconf and get an empty file for "configure"
  - From: Adam Megacz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]