On Fri, Feb 04, 2005 at 07:56:10AM -0800, Kamal R. Prasad wrote:
> 
> --- Jachym Holecek <freza@liberouter.org> wrote:
> 
> > Hi,
> > 
> > >  I downloaded netbsd 2.0 src tree on an i386
> > system
> > > running netbsd 2.0 (from the iso image). I did a
> > > #./build.sh distribution
> > > #./build.sh install=/
> > > 
> > > That presumably installed a perfect distribution
> > of
> > > netbsd 2.0. When I ran autoconf in
> > src/gnu/dist/gcc, [...]
> > 
> > Just out of curiosity -- why?
> > 
> 
> I am adding a new target (blackfin) into gcc, which
> requires modifying configure.in and running autoconf
> to generate configure.
> 
> > > Can someone help me with getting autoconf+m4
> > > functional on netbsd i386? It should be pretty
> > > straightfwd if it is part of the distribution.
> > 
> > What about ${pkgsrc}/devel/autoconf{213,}? I don't
> > think autoconf is
> > in the base system.
> > 
> autoconf is in gnu.tar.gz. Why wouldn't you want it to
> be part of the system? Or rather, how do others
> generate configure scripts on netbsd?

That's included because tools/compat/configure exists. For gcc I'll bet
you need the most recent autoconf, gnu m4, automake, etc to reconfigure it
and for that you should use pkgsrc.

James