This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: On libtool patches for 3.0.1
- To: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: On libtool patches for 3.0.1
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 11 Jul 2001 01:44:53 -0300
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Michael Elizabeth Chastain <chastain at cygnus dot com>, Mark Kettenis <kettenis at wins dot uva dot nl>, Jeff Sturm <jsturm at one-point dot com>
- Organization: GCC Team, Red Hat
- References: <215020000.994823827@warlock.codesourcery.com>
On Jul 11, 2001, Mark Mitchell <mark@codesourcery.com> wrote:
> I don't understand why
> we would change machine-generated files,
ltmain.sh is generated from ltmain.in. ltconfig used to be generated
from ltconfig.in, that was folded into libtool.m4.
> I would put the changes on the mainline, too, so that in case we
> don't manage to get the new libtool before 3.1, we don't regress.
Yep.
> We should, of course, try to make sure that equivalent fixes make
> it into the new libtool. And, I agree, that we should import the
> new libtool on the mainline when it is ready.
> Did that help?
Yup, thanks.
My only remaining doubt is whether we should wait until the
corresponding patches make it to libtool mainline before having them
approved for GCC, or if it's ok to bend the rules a bit further, yet
with the risk of my accidentally reverting those changes next time I
import from libtool, in case they still haven't made it to libtool
mainline.
--
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