This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: how to run automake/conf on newlib
- From: "J. Johnston" <jjohnstn at redhat dot com>
- To: Joel Sherrill <joel dot sherrill at OARcorp dot com>
- Cc: newlib at sources dot redhat dot com
- Date: Fri, 19 Jul 2002 15:56:55 -0400
- Subject: Re: how to run automake/conf on newlib
- Organization: Red Hat Inc.
- References: <3D385576.410BCB39@OARcorp.com>
Joel Sherrill wrote:
>
> Hi,
>
> I am trying to add a file to a machine subdirectory and wanted
> to know what was the proper command sequence to regenerate
> auto* generated files.
>
> Also are there any particular auto* version requirements?
>
> Thanks.
>
> --
> Joel Sherrill, Ph.D. Director of Research & Development
> joel@OARcorp.com On-Line Applications Research
> Ask me about RTEMS: a free RTOS Huntsville AL 35805
> Support Available (256) 722-9985
The steps in the machine/xxx dir would be:
1. aclocal -I ../../.. /* the -I ../../.. points to the top-level newlib dir */
2. autoconf
3. automake --cygnus Makefile
Step 1 above has a dependency on newlib/acinclude.m4 and configure.in.
Step 2 is dependent on configure.in and aclocal.m4. Step 3 is dependent on
Makefile.am, configure.in, and aclocal.m4. Simply put: if you do any step
because of a change, all steps after it should be done as well.
You should only have to redo aclocal if the top-level acinclude.m4 changes
or you change macros you are using in your configure.in. You don't have to
guard against the latter case by running aclocal - just be aware of it if autoconf
complains about a missing macro after you make a configure.in change.
We currently use autoconf 2.13 and automake 1.4.
-- Jeff J.