Problems building gcc with Cygwin

[Frank Szczerba]

Probably the reason is that while most every package uses the _output_ of
autoconf (the configure script in particular), most packages have no need to
regenerate that output. That is something the packager normally does, and
then only when the configure process is changed. The GNU recommendation is
that distributions do not depend on autoconf being installed unless the user
does a 'make distclean'. On the other hand, seeing as how Cygwin is mostly
used (AFAIK) by developers, it seems that autoconf would be useful to
include. Do they include gnu m4 (autoconf needs it)?

Frank

----- Original Message -----
From: "Mike Davies" <mike.davies at epid.eurotherm.co.uk>
To: <rtems-users at oarcorp.com>
Sent: Tuesday, June 13, 2000 7:08 AM
Subject: Re: Problems building gcc with Cygwin


> >
> >I asked on the cgywin list if autoconf could be included in the standard
> >distribution of cygwin but it was rejected.
>
>
> Did they give a reason for this ?   It seems as if almost every sourceware
> package on the planet depends on autoconf,  and it's not especially big
:-)
>
>
> Mike Davies
>
>
>
>
>