public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: gcc@gcc.gnu.org
Cc: binutils@sourceware.cygnus.com
Subject: New libtool for GCC 3.1?
Date: Fri, 30 Nov 2001 14:33:00 -0000	[thread overview]
Message-ID: <200111302233.OAA22500@hpsje.cup.hp.com> (raw)
Message-ID: <20011130143300.0q8VsT7uPgWjTbg-FQ_tNuaPGDaUI0qgSCJdhUAPGgc@z> (raw)

I was wondering if libtool was going to be updated from the official
sources before the release of GCC 3.1?  I tried it on my system (HP-UX
11.00) and didn't have too many problems once I figured out what to do.
The main thing I found was that I needed to use automake 1.5 instead of
an older one in order to get AM_PROG_LIBTOOL to expand properly and not
generate a reference (from the configure script) to ltconfig, which no
longer exists in the latest libtool.

So here is what I did:
	I installed automake 1.5 and autoconf 2.52 on my system
	I removed ltcf-c.sh, ltcf-cxx.sh, ltcf-gcj.sh, and ltconfig
		from the gcc directory.
	I updated libtool.m4 and ltmain.sh in the gcc directory from
		the libtool top-of-tree.
	I ran automake and autoconf in gcc/libstdc++-v3.
	I did a build.

libstdc++-v3 seems to be the only directory that I configure that uses
libtool since I am not building java but I did the same steps with the
binutils sources and ran automake;autoconf in the bfd, binutils, gas,
gprof, and opcodes directories and they built fine as well.

My main interest in all this is that support for the IA64 HP-UX platform
is in the latest libtool but not in the binutils/GCC libtools and I
would like to get it included.  I could do a patch for the libtool in
GCC/binutils but if we update libtool to the official sources then I 
will not need to do that.

Steve Ellcey
sje@cup.hp.com

             reply	other threads:[~2001-11-30 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 17:42 Steve Ellcey [this message]
2001-11-30 14:33 ` Steve Ellcey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200111302233.OAA22500@hpsje.cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).