From: Daniel Jacobowitz <drow@false.org>
To: Steve Ellcey <sje@cup.hp.com>
Cc: insight@sourceware.org, binutils@sourceware.org,
gdb@sourceware.org, sid@sourceware.org
Subject: Re: Update configure in tk/tcl/itcl
Date: Wed, 12 Jul 2006 16:27:00 -0000 [thread overview]
Message-ID: <20060712162704.GA22834@nevyn.them.org> (raw)
In-Reply-To: <200606201759.KAA00736@hpsje.cup.hp.com>
On Tue, Jun 20, 2006 at 10:59:09AM -0700, Steve Ellcey wrote:
>
> The last three src subdirectories that still use the old autoconf 2.19
> are tk, tcl, and itcl. This patch is to update the autoconf used by
> those subdirectories. Since dejagnu is no longer in the src tree I
> believe that insight is the only user of these directories and according
> to MAINTAINERS is the group that needs to approve this patch to use a
> newer autoconf. I included gdb and binutils on the email to give it
> more visibility and sid because they do show a dependency on tcl (in
> CVSROOT/modules), though that may just be an old dejagnu depenency.
>
> The alpha versions of tk/tcl 8.5 use autoconf 2.59, as do the latest
> itcl sources so updating our version in advance of those releases
> shouldn't result in an long term ongoing maintanance issue.
>
> I tested these changes on hppa1.1-hp-hpux11.11 by building insight and
> it built with no problems.
>
> Ok for checkin?
Steve, did you ever get any response from this patch? I don't want to
let the autoconf upgrade get stalled. I think it's reasonable to go
ahead and commit this if none of the Insight maintainers explicitly
object.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-12 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 17:59 Steve Ellcey
2006-07-12 16:27 ` Daniel Jacobowitz [this message]
2006-07-12 16:50 ` Steve Ellcey
2006-07-12 17:21 ` Keith Seitz
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=20060712162704.GA22834@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=insight@sourceware.org \
--cc=sid@sourceware.org \
--cc=sje@cup.hp.com \
/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).