From: Steve Ellcey <sje@cup.hp.com>
To: insight@sourceware.org
Subject: autoconf version of itcl/tcl/tk subdirectories
Date: Mon, 20 Mar 2006 22:03:00 -0000 [thread overview]
Message-ID: <200603202203.OAA13392@hpsje.cup.hp.com> (raw)
I was wondering if someone on this mailing list could help me understand
why the itcl, tcl, and tk subdirectories of the src tree are still using
autoconf 2.13. My understanding is that these subdirectories are used
when building insight, is that correct? That is why I am asking on this
email list.
The reason I am interested is that I want to get the libtool that is in
the GCC tree updated. I have been told this cannot happen until all of
the GCC and src trees have been updated to autoconf 2.59. The GCC tree
has been completely updated and most of the src tree is updated, but
itcl, tcl, and tk are among the src subdirectories that have not been
updated.
Does anyone know any blocks to updating these directories to use
autoconf 2.59?
Steve Ellcey
sje@cup.hp.com
next reply other threads:[~2006-03-20 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 22:03 Steve Ellcey [this message]
2006-03-21 0:28 ` Keith Seitz
2006-03-27 19:34 ` Steve Ellcey
2006-03-29 17:57 ` Keith Seitz
2006-03-29 18:20 ` Steve Ellcey
2006-03-29 18:30 ` Keith Seitz
2006-03-29 18:43 ` 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=200603202203.OAA13392@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=insight@sourceware.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).