initial patch to install libiberty headers

[Alexandre Oliva]

On Jan  8, 2001, DJ Delorie <dj@redhat.com> wrote:

> I thought --enable/--disable was for whether or not a package was
> *used* in the build, so --disable-libiberty would try to build gcc
> without libiberty (of course, since that isn't supported it wouldn't
> actually do that).

That's right.  --enable/--disable has to do with enabling or disabling
features in the package that's going to be installed.  However, since
it doesn't make sense to build GCC, for example, without libiberty, we
might as well take it as meaning that we'll just disable it's
installation.

> We could get by with --enable-install-libiberty if we want to stick
> with constructs autoconf already understands.

Sounds reasonable to me.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me