Problem with automake

Thomas Fitzsimmons
Fri Apr 26 11:56:00 GMT 2002

On Fri, 2002-04-26 at 08:21, Stefan Heinzmann wrote:
> Hi all,

> I understand that when I change any or in one
> of the subdirectories in the newlib source, I have to rerun autoconf
> and automake from the toplevel directory and it will find and process
> all respective files in the subdirectory tree. Is this the case?

Confusingly enough, in the top-level directory (src/) is
NOT an autoconf file.  Running autoconf in this directory will produce
an empty configure file.  Don't run any of the autotools in this
directory.  You shouldn't need to make any newlib-related changes here

When you change a file in the newlib sources, you must run
automake --cygnus to regenerate the corresponding  automake
requires a to be present in the directory in which it is
run.  So where you run automake depends on where the closest resides.

For example:

src/newlib/libc/ contains and files.
If you change src/newlib/libc/, run automake --cygnus there.
If you change src/newlib/libc/ctype/, run automake --cygnus
in src/newlib/libc/ again.  automake will go through the subdirectories
listed in src/newlib/libc/'s SUBDIRS variable, and regenerate
all the's accordingly.

The --cygnus option is required in newlib so that certain tools we use
during the build process will be searched for in the build tree as well
as in the PATH environment variable.

When you change a, run automake --cygnus (since the
generated depend on, and then autoconf in
its directory.

Hope this helps,
> Cheers
> Stefan
> __________________________________________________________________
> Gesendet von Yahoo! Mail -
> Sie brauchen mehr Speicher für Ihre E-Mails? -
Thomas Fitzsimmons
Red Hat Canada Limited        e-mail:
2323 Yonge Street, Suite 300
Toronto, ON M4P2C9

More information about the Newlib mailing list