This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: updating libtool, etc.
- From: Kelley Cook <kcook34 at ford dot com>
- To: Geoffrey Keating <geoffk at apple dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Fri, 01 Jul 2005 10:43:49 -0400
- Subject: Re: updating libtool, etc.
- Hop-count: 1
- References: <355ABEC0-4476-489F-8C73-3051A9FA471C@apple.com>
- Reply-to: Kelley Cook <kcook at gcc dot gnu dot org>
Does anyone mind if I update libtool to the latest released version,
1.5.18, and regenerate everything with automake 1.9.5?
Sounds great if you can get it to work.
I had experimented with doing it earlier in the year, before Paolo completely redid the
libjava Makefile.am to compile directories at once thus finally eliminating the
huge commandline length problems that continually crept up for various shells.
The main problem I had then, was that the then current libtool did not know anything about fortran 95,
which promptly blew up.
Finally, I was just waiting for the RSN automake 1.9.6 release to update the tree as that version has the
FSF address updates. Though 1.9.5 wouldn't really a big deal, as by 1.9.5, the autotools folks were given
the OK to drop the copyright headers from all the m4 macro which had the side benefit of dropping the FSF
address from its generated files. 1.9.6 will include the updated copyright in its helper files, such as
COPYING, depcomp and compile. But manually updating them from automake CVS it would accomplish the same thing.
Kelley Cook