From: Alan Modra <amodra@bigpond.net.au>
To: Mike Stump <mrs@apple.com>
Cc: zack@codesourcery.com, neroden@twcny.rr.com, klee@apple.com,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
newlib@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
Date: Thu, 05 Dec 2002 16:30:00 -0000 [thread overview]
Message-ID: <20021206002606.GZ27956@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <B0AC2E70-08AB-11D7-8667-000393941EE6@apple.com>
On Thu, Dec 05, 2002 at 03:45:52PM -0800, Mike Stump wrote:
> On Thursday, December 5, 2002, at 03:19 PM, Alan Modra wrote:
> >On Thu, Dec 05, 2002 at 02:55:38PM -0800, Ian Lance Taylor wrote:
> >>Perhaps --enable-maintainer-mode could be extended to specify a PATH
> >>to use to find the tools.
> >
> >It would need to be on a per-directory basis. Something like
> >
> >--enable-maintainer-mode=\
> >"gdb:/usr/local/000227/bin,libstdc++-v3:/usr/local/oldauto/bin,*:yes"
>
> This is beyond gross. :-(
Sniff. I'm sure I could make it a lot more gross. :)
> Better to require
>
> autoconf-2.14
> autoconf
>
> and then have each directory know which one to use, and require the
> advanced user to have these.
>
> OAUTOCONF = autoconf-2.14
> AUTOCONF = autoconf
>
> and then use $(AUTOCONF) for new uses, and $(OAUTOCONF) for old uses.
>
> Also, we need a version check on the old autoconf to be sure that it
> isn't too new.
The trouble with this idea is that older autoconf and automake aren't
installed as $tool-$version, and last I checked, current autoconf
doesn't install with a version suffix. Old tools really need to be
installed with a different --prefix. Hmm, I suppose a few symbolic
links would cure that problem. What happens if you need three three
or four different versions of autoconf?
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2002-12-06 0:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 11:08 Nathanael Nerode
2002-12-05 11:31 ` Andrew Cagney
2002-12-05 13:31 ` Zack Weinberg
2002-12-05 14:29 ` Alan Modra
2002-12-05 15:14 ` Ian Lance Taylor
2002-12-05 15:32 ` Alan Modra
2002-12-05 15:45 ` Ian Lance Taylor
2002-12-05 16:26 ` Andrew Cagney
2002-12-05 15:47 ` Mike Stump
2002-12-05 16:30 ` Alan Modra [this message]
2002-12-05 16:36 ` Zack Weinberg
2002-12-08 2:48 ` Klee Dienes
2002-12-05 14:07 ` Christopher Faylor
2002-12-06 7:25 ` Maciej W. Rozycki
2002-12-08 3:23 ` Klee Dienes
2003-01-12 17:51 ` [RFC] Update to current automake/autoconf/libtool versions (take 2) Klee Dienes
2003-01-12 20:34 ` Nathanael Nerode
2003-01-12 20:54 ` Zack Weinberg
2003-01-13 10:24 ` Klee Dienes
2003-01-13 14:17 ` Zack Weinberg
2002-12-05 14:36 [RFC] Update to current automake/autoconf/libtool versions Nathanael Nerode
2002-12-05 15:19 ` Zack Weinberg
2002-12-06 9:33 ` Tom Tromey
2002-12-07 12:55 ` Alexandre Oliva
2002-12-07 13:19 ` Zack Weinberg
2002-12-09 18:57 ` Alexandre Oliva
2002-12-09 21:52 ` Geoff Keating
2002-12-08 13:48 ` Tom Tromey
2002-12-05 14:40 Joern Rennecke
2002-12-10 19:33 Henry Nelson
[not found] <20021206005522.GA11907@doctormoo>
[not found] ` <87of7sa16x.fsf@egil.codesourcery.com>
2002-12-12 13:29 ` Nathanael Nerode
2002-12-13 5:31 ` Alexandre Oliva
2003-01-01 10:39 Nathanael Nerode
[not found] <9A4230D6-1D26-11D7-BFCA-00039396EEB8@apple.com>
2003-01-12 20:20 ` Alexandre Oliva
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=20021206002606.GZ27956@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=klee@apple.com \
--cc=mrs@apple.com \
--cc=neroden@twcny.rr.com \
--cc=newlib@sources.redhat.com \
--cc=zack@codesourcery.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).