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]
Other format:	[Raw text]

Re: Documenting tools necessary for GCC [draft]

From: Alexandre Oliva <aoliva at redhat dot com>
To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, gcc at gcc dot gnu dot org
Date: 30 May 2003 17:22:30 -0300
Subject: Re: Documenting tools necessary for GCC [draft]
Organization: GCC Team, Red Hat
References: <200305291727.NAA06347@caip.rutgers.edu><Pine.LNX.4.53.0305291835450.23254@kern.srcf.societies.cam.ac.uk>

On May 29, 2003, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:

> Not included in the above list:

> libtool (a tricky case because what's used is based on a dead CVS branch).

Nobody needs anything from libtool that's not in the GCC tree.  The m4
macros used by autoconf are pulled from the top-level libtool.m4.  The
scripts used by libtool (ltconfig, ltmain.sh, ltcf-*.sh) are all used
from the top-level.  There's no need for anyone to have any libtool
version installed elsewhere, for build or development.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer

References:
- Documenting tools necessary for GCC [draft]
  - From: Kaveh R. Ghazi
- Re: Documenting tools necessary for GCC [draft]
  - From: Joseph S. Myers

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