This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: initial patch to install libiberty headers
On Jan 8, 2001, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> On Fri, Jan 05, 2001 at 07:14:01PM -0500, DJ Delorie wrote:
> I was kind of hoping to keep the names in the set usable with autoconf
> macros, and --install-* isn't in that set, I think. The yes/no/path thing
> works well, though.
IIRC, the original purpose of --enable/disable was to control whether
to install part of a package or not. That's what I'd use. IMO, we
should arrange for the top-level configure to pass down
--disable-libiberty unless it sees --enable-libiberty in the command
line, so that libiberty's configure.in can default to having it
installed, and then libiberty can be distributed as a stand-alone
package, which I consider a good idea.
--
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