From: Benjamin Kosnik <bkoz@redhat.com>
To: gcc@gcc.gnu.org
Cc: nickc@redhat.com, neroden@twcny.rr.com
Subject: Re: Planning for the Autoconf 2.5x transition?
Date: Thu, 02 Jan 2003 17:15:00 -0000 [thread overview]
Message-ID: <20030102111450.79ce1439.bkoz@redhat.com> (raw)
> > 1. Make all directories have configure.in scripts which work
> > correctly with *both* 2.13 and 2.5x, then switch over.
>I would prefer this scheme.
I think this way lies continued stalemate. I don't see how both can be
made to work, and, if this cannot be accomplished (we have attempted
this for libstdc++), I'd rather have things work sanely with autoconf
2.5.x. It is an incredible inconvenience for me to not be able to use
the default autotools on RH 8 for libstdc++ work: because of this, I'm
motivated to get this working for libstdc++ as soon as possible.
I think a much saner approach is to take the target subdirs on a case by
case basis.
Are all the target libs able to auto-gen configure/Makefiles with the
exact same autoconf/automake at the moment? That would surprise me.
-benjamin
next reply other threads:[~2003-01-02 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 17:15 Benjamin Kosnik [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-24 6:11 Nathanael Nerode
2002-12-26 5:47 ` Alexandre Oliva
2002-12-26 6:12 ` Phil Edwards
2002-12-30 7:34 ` Nick Clifton
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=20030102111450.79ce1439.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@twcny.rr.com \
--cc=nickc@redhat.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).