This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: initial patch to install libiberty headers

To: pedwards at disaster dot jaj dot com
Subject: Re: initial patch to install libiberty headers
From: DJ Delorie <dj at redhat dot com>
Date: Fri, 5 Jan 2001 19:14:01 -0500
CC: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
References: <20010102180811.A1612@disaster.jaj.com> <20010105191031.B15643@disaster.jaj.com> <200101060004.TAA18323@greed.delorie.com> <20010105191940.A15918@disaster.jaj.com>


> Okay; spelled how?

If it were me, I'd allow these:
	--install-libiberty
	--install-libiberty=[yes|no] (uses $prefix)
	--install-libiberty=/path    (overrides $prefix)

> Such as?  (For inclusion into the liberty manual; I'm not doubting you.)

If you install gcc, gdb, and binutils, they each install their own
version of libiberty.  Which is the correct one?  The fact that
libiberty comes with so many packages (from different branches in the
worst case) as a helper makes it a bad idea to install it by default.

Follow-Ups:
- Re: initial patch to install libiberty headers
  - From: Phil Edwards

References:
- forget *documenting* libiberty -- how about *installing* it?
  - From: Phil Edwards
- initial patch to install libiberty headers
  - From: Phil Edwards
- Re: initial patch to install libiberty headers
  - From: DJ Delorie
- Re: initial patch to install libiberty headers
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]